Systems and methods for managing resource utilization in a network of moving things, for example including autonomous vehicles

ABSTRACT

Communication network architectures, systems and methods for supporting a network of mobile nodes. As a non-limiting example, various aspects of this disclosure provide communication network architectures, systems, and methods for managing resource utilization in a network of moving things, for example including autonomous vehicles.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This patent application makes reference to, claims priority to, andclaims benefit from U.S. Provisional Patent Application Ser. No.62/563,229, filed on Sep. 26, 2017, and titled “Systems and Methods forManaging Resource Utilization in a Network of Moving Things, for ExampleIncluding Autonomous Vehicles,” which is hereby incorporated herein byreference in its entirety.

This patent application is related to U.S. Provisional PatentApplication Ser. No. 62/222,192, filed on Sep. 22, 2015, and titled“Communication Network of Moving Things,” which is hereby incorporatedherein by reference in its entirety. The present application is alsorelated to U.S. Provisional Application Ser. No. 62/221,997, titled“Integrated Communication Network for a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,016,titled “Systems and Methods for Synchronizing a Network of MovingThings,” filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,042, titled “Systems and Methods for Managing a Network of MovingThings,” filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,066, titled “Systems and Methods for Monitoring a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,077, titled “Systems and Methods for Detecting andClassifying Anomalies in a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,098, titled “Systemsand Methods for Managing Mobility in a Network of Moving Things,” filedon Sep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,121,titled “Systems and Methods for Managing Connectivity a Network ofMoving Things,” filed on Sep. 22, 2015; U.S. Provisional ApplicationSer. No. 62/222,135, titled “Systems and Methods for Collecting SensorData in a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015; U.S. Provisional Application Ser. No. 62/222,150, titled “Systemsand Methods for Interfacing with a User of a Network of Moving Things,”filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,168, titled “Systems and Methods for Data Storage and Processingfor a Network of Moving Things,” filed on Sep. 22, 2015; U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015; U.S. Provisional Application Ser. No. 62/222,186, titled“Systems and Methods for Environmental Management in a Network of MovingThings,” filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/222,190, titled “Systems and Methods for Port Management in a Networkof Moving Things,” filed on Sep. 22, 2015; U.S. Provisional PatentApplication Ser. No. 62/222,192, titled “Communication Network of MovingThings,” filed on Sep. 22, 2015; U.S. Provisional Application Ser. No.62/244,828, titled “Utilizing Historical Data to Correct GPS Data in aNetwork of Moving Things,” filed on Oct. 22, 2015; U.S. ProvisionalApplication Ser. No. 62/244,930, titled “Using Anchors to Correct GPSData in a Network of Moving Things,” filed on Oct. 22, 2015; U.S.Provisional Application Ser. No. 62/246,368, titled “Systems and Methodsfor Inter-Application Communication in a Network of Moving Things,”filed on Oct. 26, 2015; U.S. Provisional Application Ser. No.62/246,372, titled “Systems and Methods for Probing and ValidatingCommunication in a Network of Moving Things,” filed on Oct. 26, 2015;U.S. Provisional Application Ser. No. 62/250,544, titled “Adaptive RateControl for Vehicular Networks,” filed on Nov. 4, 2015; U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015; U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015; U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015; U.S. Provisional Application Ser. No. 62/265,267, titled “Systemsand Methods for Improving Coverage and Throughput of Mobile AccessPoints in a Network of Moving Things,” filed on Dec. 9, 2015; U.S.Provisional Application Ser. No. 62/270,858, titled “ChannelCoordination in a Network of Moving Things,” filed on Dec. 22, 2015;U.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015; U.S. Provisional Application Ser. No.62/260,749, titled “Systems and Methods for Improving Fixed Access PointCoverage in a Network of Moving Things,” filed on Nov. 30, 2015; U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015; U.S. ProvisionalApplication Ser. No. 62/281,432, titled “Systems and Methods forManaging and Triggering Handovers of Mobile Access Points in a Networkof Moving Things,” filed on Jan. 21, 2016; U.S. Provisional ApplicationSer. No. 62/268,188, titled “Captive Portal-related Control andManagement in a Network of Moving Things,” filed on Dec. 16, 2015; U.S.Provisional Application Ser. No. 62/270,678, titled “Systems and Methodsto Extrapolate High-Value Data from a Network of Moving Things,” filedon Dec. 22, 2015; U.S. Provisional Application Ser. No. 62/272,750,titled “Systems and Methods for Remote Software Update and Distributionin a Network of Moving Things,” filed on Dec. 30, 2015; U.S. ProvisionalApplication Ser. No. 62/278,662, titled “Systems and Methods for RemoteConfiguration Update and Distribution in a Network of Moving Things,”filed on Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,243, titled “Systems and Methods for Adapting a Network of MovingThings Based on User Feedback,” filed on Jan. 22, 2016; U.S. ProvisionalApplication Ser. No. 62/278,764, titled “Systems and Methods toGuarantee Data Integrity When Building Data Analytics in a Network ofMoving Things,” Jan. 14, 2016; U.S. Provisional Application Ser. No.62/286,515, titled “Systems and Methods for Self-Initialization andAutomated Bootstrapping of Mobile Access Points in a Network of MovingThings,” filed on Jan. 25, 2016; U.S. Provisional Application Ser. No.62/295,602, titled “Systems and Methods for Power Management in aNetwork of Moving Things,” filed on Feb. 16, 2016; and U.S. ProvisionalApplication Ser. No. 62/299,269, titled “Systems and Methods forAutomating and Easing the Installation and Setup of the InfrastructureSupporting a Network of Moving Things,” filed on Feb. 24, 2016; each ofwhich is hereby incorporated herein by reference in its entirety for allpurposes.

This application is also related to U.S. patent application Ser. No.15/616,337, filed Jun. 7, 2017, and titled “SYSTEMS AND METHODS FORMANAGING CONTAINERS IN A NETWORK OF MOVING THINGS,” the entirety ofwhich is hereby incorporated herein by reference for all purposes.

BACKGROUND

Current communication networks are unable to adequately supportcommunication environments involving mobile and static nodes. As anon-limiting example, current communication networks are unable toadequately support a network comprising a complex array of both movingand static nodes (e.g., the Internet of moving things, autonomousvehicle networks, etc.). Limitations and disadvantages of conventionalmethods and systems will become apparent to one of skill in the art,through comparison of such approaches with some aspects of the presentmethods and systems set forth in the remainder of this disclosure withreference to the drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 2 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIG. 3 shows a diagram of a metropolitan area network, in accordancewith various aspects of this disclosure.

FIG. 4 shows a block diagram of a communication network, in accordancewith various aspects of this disclosure.

FIGS. 5A-5C show a plurality of network configurations illustrating theflexibility and/or and resiliency of a communication network, inaccordance with various aspects of this disclosure.

FIG. 6 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 7 shows a block diagram of an example communication network, inaccordance with various aspects of the present disclosure.

FIG. 8 shows a block diagram of an example Cloud-basedVehicle-network-as-a-service (VNAAS) Gatekeeper and network, inaccordance with various aspects of the present disclosure.

FIG. 9 shows a block diagram of an example Mobile Computing Node (MCN)and network, in accordance with various aspects of the presentdisclosure.

FIG. 10 shows a flow diagram of an application life cycle, in accordancewith various aspects of the present disclosure.

FIG. 11 shows a block diagram of a network node, in accordance withvarious aspects of the present disclosure.

SUMMARY

Various aspects of this disclosure provide communication networkarchitectures, systems and methods for supporting a network of mobilenodes. As a non-limiting example, various aspects of this disclosureprovide communication network architectures, systems, and methods formanaging resource utilization in a network of moving things, for exampleincluding autonomous vehicles.

DETAILED DESCRIPTION OF VARIOUS ASPECTS OF THE DISCLOSURE

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or z” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of one or more non-limitingexamples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

With the proliferation of the mobile and/or static things (e.g.,devices, machines, people, etc.) and logistics for such things to becomeconnected to each other (e.g., in the contexts of smart logistics,transportation, environmental sensing, etc.), a platform that is forexample always-on, robust, scalable and secure that is capable ofproviding connectivity, services and Internet access to such things (orobjects), anywhere and anytime is desirable. Efficient power utilizationwithin the various components of such system is also desirable.

Accordingly, various aspects of the present disclosure provide afully-operable, always-on, responsive, robust, scalable, secureplatform/system/architecture to provide connectivity, services andInternet access to all mobile things and/or static things (e.g.,devices, machines, people, access points, end user devices, sensors,etc.) anywhere and anytime, while operating in an energy-efficientmanner.

Various aspects of the present disclosure provide a platform that isflexibly configurable and adaptable to the various requirements,features, and needs of different environments, where each environmentmay be characterized by a respective level of mobility and density ofmobile and/or static things, and the number and/or types of access tothose things. Characteristics of various environments may, for example,include high mobility of nodes (e.g., causing contacts or connections tobe volatile), high number of neighbors, high number of connected mobileusers, mobile access points, availability of multiple networks andtechnologies (e.g., sometimes within a same area), etc. For example, themode of operation of the platform may be flexibly adapted fromenvironment to environment, based on each environment's respectiverequirements and needs, which may be different from other environments.Additionally for example, the platform may be flexibly optimized (e.g.,at design/installation time and/or in real-time) for different purposes(e.g., to reduce the latency, increase throughput, reduce powerconsumption, load balance, increase reliability, make more robust withregard to failures or other disturbances, etc.), for example based onthe content, service or data that the platform provides or handleswithin a particular environment.

In accordance with various aspects of the present disclosure, manycontrol and management services (e.g., mobility, security, routing,etc.) are provided on top of the platform (e.g., directly, using controloverlays, using containers, etc.), such services being compatible withthe services currently deployed on top of the Internet or othercommunication network(s).

The communication network (or platform), in whole or in part, may forexample be operated in public and/or private modes of operation, forexample depending on the use case. The platform may, for example,operate in a public or private mode of operation, depending on theuse-case (e.g., public Internet access, municipal environment sensing,fleet operation, etc.).

Additionally for example, in an implementation in which various networkcomponents are mobile, the transportation and/or signal controlmechanisms may be adapted to serve the needs of the particularimplementation. Also for example, wireless transmission power and/orrate may be adapted (e.g., to mitigate interference, to reduce powerconsumption, to extend the life of network components, etc.

Various example implementations of a platform, in accordance withvarious aspects of the present disclosure, are capable of connectingdifferent subsystems, even when various other subsystems that maynormally be utilized are unavailable. For example, the platform maycomprise various built-in redundancies and fail-recovery mechanisms. Forexample, the platform may comprise a self-healing capability,self-configuration capability, self-adaptation capability, etc. Theprotocols and functions of the platform may, for example, be prepared tobe autonomously and smoothly configured and adapted to the requirementsand features of different environments characterized by different levelsof mobility and density of things (or objects), the number/types ofaccess to those things. For example, various aspects of the platform maygather context parameters that can influence any or all decisions. Suchparameters may, for example, be derived locally, gathered from aneighborhood, fixed APs, the Cloud, etc. Various aspects of the platformmay also, for example, ask for historical information to feed any of thedecisions, where such information can be derived from historical data,from surveys, from simulators, etc. Various aspects of the platform mayadditionally, for example, probe or monitor decisions made throughoutthe network, for example to evaluate the network and/or the decisionsthemselves in real-time. Various aspects of the platform may further,for example, enforce the decisions in the network (e.g., afterevaluating the probing results). Various aspects of the platform may,for example, establish thresholds to avoid any decision that is to beconstantly or repeatedly performed without any significant advantage(e.g., technology change, certificate change, IP change, etc.). Variousaspects of the platform may also, for example, learn locally (e.g., withthe decisions performed) and dynamically update the decisions.

In addition to (or instead of) failure robustness, a platform mayutilize multiple connections (or pathways) that exist between distinctsub-systems or elements within the same sub-system, to increase therobustness and/or load-balancing of the system.

The following discussion will present examples of the functionalityperformed by various example subsystems of the communication network. Itshould be understood that the example functionality discussed hereinneed not be performed by the particular example subsystem or by a singlesubsystem. For example, the subsystems present herein may interact witheach other, and data or control services may be deployed either in acentralized way, or having their functionalities distributed among thedifferent subsystems, for example leveraging the cooperation between theelements of each subsystem.

Various aspects of the present disclosure provide a communicationnetwork (e.g., a city-wide vehicular network, a shipping port-sizedvehicular network, a campus-wide vehicular network, etc.) that utilizesvehicles (e.g., automobiles, buses, trucks, boats, forklifts,human-operated vehicles, autonomous and/or remote controlled vehicles,etc.) as Wi-Fi hotspots. Note that Wi-Fi is generally used throughoutthis discussion as an example, but the scope of various aspects of thisdisclosure is not limited thereto. For example, other wireless LANtechnologies, PAN technologies, MAN technologies, etc., may be utilized.Such utilization may, for example, provide cost-effective ways to gathersubstantial amounts of urban data, and provide for the efficientoffloading of traffic from congested cellular networks (or othernetworks). In controlled areas (e.g., ports, harbors, etc.) with manyvehicles, a communication network in accordance with various aspects ofthis disclosure may expand the wireless coverage of existing enterpriseWi-Fi networks, for example providing for real-time communication withvehicle drivers (e.g., human, computer-controlled, etc.) and othermobile employees without the need for SIM cards or cellular (or othernetwork) data plans.

Vehicles may have many advantageous characteristics that make themuseful as Wi-Fi (or general wireless) hotspots. For example, vehiclesgenerally have at least one battery, vehicles are generally denselyspread over the city at street level and/or they are able to establishmany contacts with each other in a controlled space, and vehicles cancommunicate with 10 x the range of normal Wi-Fi in the 5.9 GHz frequencyband, reserved for intelligent transportation systems in the EU, theU.S., and elsewhere. Note that the scope of this disclosure is notlimited to such 5.9 GHz wireless communication. Further, vehicles areable to effectively expand their coverage area into a swath over aperiod of time, enabling a single vehicle access point to interact withsubstantially more data sources over the period of time.

In accordance with various aspects of the present disclosure, anaffordable multi-network on-board unit (OBU) is presented. Note that theOBU may also be referred to herein as a mobile access point, Mobile AP,MAP, etc. The OBU may, for example, comprise a plurality of networkinginterfaces (e.g., Wi-Fi, 802.11p, 4G, Bluetooth, UWB, etc.). The OBUmay, for example, be readily installed in or on private and/or publicvehicles (e.g., individual user vehicles, vehicles of private fleets,vehicles of public fleets, etc.). The OBU may, for example, be installedin transportation fleets, waste management fleets, law enforcementfleets, emergency services, road maintenance fleets, taxi fleets,aircraft fleets, etc. The OBU may, for example, be installed in or on avehicle or other structure with free mobility or relatively limitedmobility. The OBU may also, for example, be carried by a person orservice animal, mounted to a bicycle, mounted to a moving machine ingeneral, mounted to a container, etc.

The OBUs may, for example, operate to connect passing vehicles to thewired infrastructure of one or more network providers, telecomoperators, etc. In accordance with the architecture, hardware, andsoftware functionality discussed herein, vehicles and fleets can beconnected not just to the cellular networks (or other wide area ormetropolitan area networks, etc.) and existing Wi-Fi hotspots spreadover a city or a controlled space, but also to other vehicles (e.g.,utilizing multi-hop communications to a wired infrastructure, single ormulti-hop peer-to-peer vehicle communication, etc.). The vehicles and/orfleets may, for example, form an overall mesh of communication links,for example including the OBUs and also fixed Access Points (APs)connected to the wired infrastructure (e.g., a local infrastructure,etc.). Note that OBUs herein may also be referred to as “Mobile APs,”“mobile hotspots,” “MAPs,” etc. Also note that fixed access points mayalso be referred to herein as Road Side Units (RSUs), Fixed APs, FAPs,etc.

In an example implementation, the OBUs may communicate with the FixedAPs utilizing a relatively long-range protocol (e.g., 802.11p, etc.),and the Fixed APs may, in turn, be hard wired to the wiredinfrastructure (e.g., via cable, tethered optical link, etc.). Note thatFixed APs may also, or alternatively, be coupled to the infrastructurevia wireless link (e.g., 802.11p, etc.). Additionally, clients or userdevices may communicate with the OBUs using one or more relativelyshort-range protocols (e.g., Wi-Fi, Bluetooth, UWB, etc.). The OBUs, forexample having a longer effective wireless communication range thantypical Wi-Fi access points or other wireless LAN/PAN access points(e.g., at least for links such as those based on 802.11p, etc.), arecapable of substantially greater coverage areas than typical Wi-Fi orother wireless LAN/PAN access points, and thus fewer OBUs are necessaryto provide blanket coverage over a geographical area.

The OBU may, for example, comprise a robust vehicular networking module(e.g., a connection manager) which builds on long-range communicationprotocol capability (e.g., 802.11p, etc.). For example, in addition tocomprising 802.11p (or other long-range protocol) capability tocommunicate with Fixed APs, vehicles, and other nodes in the network,the OBU may comprise a network interface (e.g., 802.11a/b/g/n, 802.11ac,802.11af, any combination thereof, etc.) to provide wireless local areanetwork (WLAN) connectivity to end user devices, sensors, fixed Wi-Fiaccess points, etc. For example, the OBU may operate to providein-vehicle Wi-Fi Internet access to users in and/or around the vehicle(e.g., a bus, train car, taxi cab, public works vehicle, etc.). The OBUmay further comprise one or more wireless backbone communicationinterfaces (e.g., cellular network interfaces, etc.). Though in variousexample scenarios, a cellular network interface (or other wirelessbackbone communication interface) might not be the preferred interfacefor various reasons (e.g., cost, power, bandwidth, etc.), the cellularnetwork interface may be utilized to provide connectivity ingeographical areas that are not presently supported by a Fixed AP, maybe utilized to provide a fail-over communication link, may be utilizedfor emergency communications, may be utilized to subscribe to localinfrastructure access, etc. The cellular network interface may also, forexample, be utilized to allow the deployment of solutions that aredependent on the cellular network operators.

An OBU, in accordance with various aspects of the present disclosure,may for example comprise a smart connection manager that can select thebest available wireless link(s) (e.g., Wi-Fi, 802.11p, cellular, vehiclemesh, etc.) with which to access the Internet. The OBU may also, forexample, provide geo-location capabilities (e.g., GPS, etc.), motiondetection sensors to determine if the vehicle is in motion, and a powercontrol subsystem (e.g., to ensure that the OBU does not deplete thevehicle battery, etc.). The OBU may, for example, comprise any or all ofthe sensors (e.g., environmental sensors, etc.) discussed herein.

The OBU may also, for example, comprise a manager that managesmachine-to-machine data acquisition and transfer (e.g., in a real-timeor delay-tolerant fashion) to and from the cloud. For example, the OBUmay log and/or communicate information of the vehicles.

The OBU may, for example, comprise a connection and/or routing managerthat operates to perform routing of communications in avehicle-to-vehicle/vehicle-to-infrastructure multi-hop communication. Amobility manager (or controller, MC) may, for example, ensure thatcommunication sessions persist over one or more handoff(s) (alsoreferred to herein as a “handover” or “handovers”) (e.g., betweendifferent Mobile APs, Fixed APs, base stations, hot spots, etc.), amongdifferent technologies (e.g., 802.11p, cellular, Wi-Fi, satellite,etc.), among different MCs (e.g., in a fail-over scenario, loadredistribution scenario, etc.), across different interfaces (or ports),etc. Note that the MC may also be referred to herein as a Local MobilityAnchor (LMA), a Network Controller, etc. Note that the MC, or aplurality thereof, may for example be implemented as part of thebackbone, but may also, or alternatively, be implemented as part of anyof a variety of components or combinations thereof. For example, the MCmay be implemented in a Fixed AP (or distributed system thereof), aspart of an OBU (or a distributed system thereof), etc. Variousnon-limiting examples of system components and/or methods are providedin U.S. Provisional Application No. 62/222,098, filed Sep. 22, 2015, andtitled “Systems and Method for Managing Mobility in a Network of MovingThings,” the entire contents of which are hereby incorporated herein byreference. Note that in an example implementation including a pluralityof MCs, such MCs may be co-located and/or may be geographicallydistributed.

Various aspects of the present disclosure also provide a cloud-basedservice-oriented architecture that handles the real-time management,monitoring and reporting of the network and clients, the functionalitiesrequired for data storage, processing and management, the Wi-Fi clientauthentication and Captive Portal display, etc.

A communication network (or component thereof) in accordance withvarious aspects of the present disclosure may, for example, support awide range of smart city applications (or controlled scenarios, orconnected scenarios, etc.) and/or use-cases, as described herein.

For example, an example implementation may operate to turn each vehicle(e.g., both public and private taxis, buses, trucks, etc.) into a MobileAP (e.g., a mobile Wi-Fi hotspot), offering Internet access toemployees, passengers and mobile users travelling in the city, waitingin bus stops, sitting in parks, etc. Moreover, through an examplevehicular mesh network formed between vehicles and/or fleets ofvehicles, an implementation may be operable to offload cellular trafficthrough the mobile Wi-Fi hotspots and/or fixed APs (e.g., 802.11p-basedAPs) spread over the city and connected to the wired infrastructure ofpublic or private telecom operators in strategic places, while ensuringthe widest possible coverage at the lowest possible cost.

An example implementation (e.g., of a communication network and/orcomponents thereof) may, for example, be operable as a massive urbanscanner that gathers large amounts of data (e.g., continuously)on-the-move, actionable or not, generated by a myriad of sourcesspanning from the in-vehicle sensors or On Board Diagnostic System port(e.g., OBD2, etc.), interface with an autonomous vehicle driving system,external Wi-Fi/Bluetooth-enabled sensing units spread over the city,devices of vehicles' drivers and passengers (e.g., informationcharacterizing such devices and/or passengers, etc.), positioning systemdevices (e.g., position information, velocity information, trajectoryinformation, travel history information, etc.), etc.

Depending on the use case, the OBU may for example process (or computer,transform, manipulate, aggregate, summarize, etc.) the data beforesending the data from the vehicle, for example providing the appropriategranularity (e.g., value resolution) and sampling rates (e.g., temporalresolution) for each individual application. For example, the OBU may,for example, process the data in any manner deemed advantageous by thesystem. The OBU may, for example, send the collected data (e.g., rawdata, preprocessed data, information of metrics calculated based on thecollected data, etc.) to the Cloud (e.g., to one or more networkedservers coupled to any portion of the network) in an efficient andreliable manner to improve the efficiency, environmental impact andsocial value of municipal city operations and transportation services.Various example use cases are described herein.

In an example scenario in which public buses are moving along cityroutes and/or taxis are performing their private transportationservices, the OBU is able to collect large quantities of real-time datafrom the positioning systems (e.g., GPS, etc.), from accelerometermodules, etc. The OBU may then, for example, communicate such data tothe Cloud, where the data may be processed, reported and viewed, forexample to support such public or private bus and/or taxi operations,for example supporting efficient remote monitoring and scheduling ofbuses and taxis, respectively.

In an example implementation, small cameras (or other sensors) may becoupled to small single-board computers (SBCs) that are placed above thedoors of public buses to allow capturing image sequences of peopleentering and leaving buses, and/or on stops along the bus routes inorder to estimate the number of people waiting for a bus. Such data maybe gathered by the OBU in order to be sent to the Cloud. With such data,public transportation systems may detect peaks; overcrowded buses,routes and stops; underutilized buses, routes and stops; etc., enablingaction to be taken in real-time (e.g., reducing bus periodicity todecrease fuel costs and CO₂ emissions where and when passenger flows aresmaller, etc.) as well as detecting systematic transportation problems.

An OBU may, for example, be operable to communicate with any of avariety of Wi-Fi-enabled sensor devices equipped with a heterogeneouscollection of environmental sensors. Such sensors may, for example,comprise noise sensors (microphones, etc.), gas sensors (e.g., sensingCO, NO₂, O₃, volatile organic compounds (or VOCs), CO₂, etc.), smokesensors, pollution sensors, meteorological sensors (e.g., sensingtemperature, humidity, luminosity, particles, solar radiation, windspeed (e.g., anemometer), wind direction, rain (e.g., a pluviometer),optical scanners, biometric scanners, cameras, microphones, etc.). Suchsensors may also comprise sensors associated with users (e.g., vehicleoperators or passengers, passersby, etc.) and/or their personal devices(e.g., smart phones or watches, biometrics sensors, wearable sensors,implanted sensors, etc.). Such sensors may, for example, comprisesensors and/or systems associated with on-board diagnostic (OBD) unitsfor vehicles, autonomous vehicle driving systems, etc. Such sensors may,for example, comprise positioning sensors (e.g., GPS sensors, Galileosensors, GLONASS sensors, etc.). Note that such positioning sensors maybe part of a vehicle's operational system (e.g., a localhuman-controlled vehicle, an autonomous vehicle, a remotehuman-controlled vehicle, etc.) Such sensors may, for example, comprisecontainer sensors (e.g., garbage can sensors, shipping containersensors, container environmental sensors, container tracking sensors,etc.).

Once a vehicle enters the vicinity of such a sensor device, a wirelesslink may be established, so that the vehicle (or OBU thereof) cancollect sensor data from the sensor device and upload the collected datato a database in the Cloud. The appropriate action can then be taken. Inan example waste management implementation, several waste management (orcollection) trucks may be equipped with OBUs that are able toperiodically communicate with sensors installed on containers in orderto gather information about waste level, time passed since lastcollection, etc. Such information may then sent to the Cloud (e.g., to awaste management application coupled to the Internet, etc.) through thevehicular mesh network, in order to improve the scheduling and/orrouting of waste management trucks. Note that various sensors may alwaysbe in range of the Mobile AP (e.g., vehicle-mounted sensors). Note thatthe sensor may also (or alternatively) be mobile (e.g., a sensor mountedto another vehicle passing by a Mobile AP or Fixed AP, a drone-mountedsensor, a pedestrian-mounted sensor, etc.).

In an example implementation, for example in a controlled space (e.g., aport, harbor, airport, factory, plantation, mine, etc.) with manyvehicles, machines and employees, a communication network in accordancewith various aspects of the present disclosure may expand the wirelesscoverage of enterprise and/or local Wi-Fi networks, for example withoutresorting to a Telco-dependent solution based on SIM cards or cellularfees. In such an example scenario, apart from avoiding expensivecellular data plans, limited data rate and poor cellular coverage insome places, a communication network in accordance with various aspectsof the present disclosure is also able to collect and/or communicatelarge amounts of data, in a reliable and real-time manner, where suchdata may be used to optimize harbor logistics, transportationoperations, etc.

For example in a port and/or harbor implementation, by gatheringreal-time information on the position, speed, fuel consumption and CO₂emissions of the vehicles, the communication network allows a portoperator to improve the coordination of the ship loading processes andincrease the throughput of the harbor. Also for example, thecommunication network enables remote monitoring of drivers' behaviors,behaviors of autonomous vehicles and/or control systems thereof, trucks'positions and engines' status, and then be able to provide real-timenotifications to drivers (e.g., to turn on/off the engine, follow theright route inside the harbor, take a break, etc.), for example humandrivers and/or automated vehicle driving systems, thus reducing thenumber and duration of the harbor services and trips. Harbor authoritiesmay, for example, quickly detect malfunctioning trucks and abnormaltrucks' circulation, thus avoiding accidents in order to increase harborefficiency, security, and safety. Additionally, the vehicles can alsoconnect to Wi-Fi access points from harbor local operators, and provideWi-Fi Internet access to vehicles' occupants and surrounding harboremployees, for example allowing pilots to save time by filing reportsvia the Internet while still on the water.

FIG. 1 shows a block diagram of a communication network 100, inaccordance with various aspects of this disclosure. Any or all of thefunctionality discussed herein may be performed by any or all of theexample components of the example network 100. Also, the example network100 may, for example, share any or all characteristics with the otherexample methods, systems, networks and/or network components 200, 300,400, 500-570, 600, 700, 800, 900, 1000, and 1100, discussed herein.

The example network 100, for example, comprises a Cloud that may, forexample comprise any of a variety of network level components. The Cloudmay, for example, comprise any of a variety of server systems executingapplications that monitor and/or control components of the network 100.Such applications may also, for example, manage the collection ofinformation from any of a large array of networked information sources,many examples of which are discussed herein. The Cloud (or a portionthereof) may also be referred to, at times, as an API. For example,Cloud (or a portion thereof) may provide one or more applicationprogramming interfaces (APIs) which other devices may use forcommunicating/interacting with the Cloud.

An example component of the Cloud may, for example, manageinteroperability with various multi-cloud systems and architectures.Another example component (e.g., a Cloud service component) may, forexample, provide various cloud services (e.g., captive portal services,authentication, authorization, and accounting (AAA) services, APIGateway services, etc.). An additional example component (e.g., aDevCenter component) may, for example, provide network monitoring and/ormanagement functionality, manage the implementation of software updates,etc. A further example component of the Cloud may manage data storage,data analytics, data access, etc. A still further example component ofthe Cloud may include any of a variety of third-partly applications andservices.

The Cloud may, for example, be coupled to the Backbone/CoreInfrastructure of the example network 100 via the Internet (e.g.,utilizing one or more Internet Service Providers). Though the Internetis provided by example, it should be understood that scope of thepresent disclosure is not limited thereto.

The Backbone/Core may, for example, comprise any one or more differentcommunication infrastructure components. For example, one or moreproviders may provide backbone networks or various components thereof.As shown in the example network 100 illustrated in FIG. 1, a Backboneprovider may provide wireline access (e.g., PSTN, fiber, cable, etc.).Also for example, a Backbone provider may provide wireless access (e.g.,Microwave, LTE/Cellular, 5G/TV Spectrum, etc.).

The Backbone/Core may also, for example, comprise one or more LocalInfrastructure Providers. The Backbone/Core may also, for example,comprise a private infrastructure (e.g., run by the network 100implementer, owner, etc.). The Backbone/Core may, for example, provideany of a variety of Backbone Services (e.g., AAA, Mobility, Monitoring,Addressing, Routing, Content services, Gateway Control services, etc.).

The Backbone/Core Infrastructure may comprise any of a variety ofcharacteristics, non-limiting examples of which are provided herein. Forexample, the Backbone/Core may be compatible with different wireless orwired technologies for backbone access. The Backbone/Core may also beadaptable to handle public (e.g., municipal, city, campus, etc.) and/orprivate (e.g., ports, campus, etc.) network infrastructures owned bydifferent local providers, and/or owned by the network implementer orstakeholder. The Backbone/Core may, for example, comprise and/orinterface with different Authentication, Authorization, and Accounting(AAA) mechanisms.

The Backbone/Core Infrastructure may, for example, support differentmodes of operation (e.g., L2 in port implementations, L3 in on-landpublic transportation implementations, utilizing any one or more of aplurality of different layers of digital IP networking, any combinationsthereof, equivalents thereof, etc.) or addressing pools. TheBackbone/Core may also for example, be agnostic to the Cloud provider(s)and/or Internet Service Provider(s). Additionally for example, theBackbone/Core may be agnostic to requests coming from any or allsubsystems of the network 100 (e.g., Mobile APs or OBUs (On BoardUnits), Fixed APs or RSUs (Road Side Units), MCs (Mobility Controllers)or LMAs (Local Mobility Anchors) or Network Controllers, etc.) and/orthird-party systems.

The Backbone/Core Infrastructure may, for example, comprise the abilityto utilize and/or interface with different data storage/processingsystems (e.g., MongoDB, MySql, Redis, etc.). The Backbone/CoreInfrastructure may further, for example, provide different levels ofsimultaneous access to the infrastructure, services, data, etc.

The example network 100 may also, for example, comprise a Fixed HotspotAccess Network. Various example characteristics of such a Fixed HotspotAccess Network 200 are shown at FIG. 2. The example network 200 may, forexample, share any or all characteristics with the other examplemethods, systems, networks and/or network components 100, 300, 400,500-570, 600, 700, 800, 900, 1000, and 1100, discussed herein.

In the example network 200, the Fixed APs (e.g., the proprietary APs,the public third party APs, the private third party APs, etc.) may bedirectly connected to the local infrastructure provider and/or to thewireline/wireless backbone. Also for example, the example network 200may comprise a mesh between the various APs via wireless technologies.Note, however, that various wired technologies may also be utilizeddepending on the implementation. As shown, different fixed hotspotaccess networks can be connected to a same backbone provider, but mayalso be connected to different respective backbone providers. In anexample implementation utilizing wireless technology for backboneaccess, such an implementation may be relatively fault tolerant. Forexample, a Fixed AP may utilize wireless communications to the backbonenetwork (e.g., cellular, 3G, LTE, other wide or metropolitan areanetworks, etc.) if the backhaul infrastructure is down. Also forexample, such an implementation may provide for relatively easyinstallation (e.g., a Fixed AP with no cable power source that can beplaced virtually anywhere).

In the example network 200, the same Fixed AP can simultaneously provideaccess to multiple Fixed APs, Mobile APs (e.g., vehicle OBUs, etc.),devices, user devices, sensors, things, etc. For example, a plurality ofmobile hotspot access networks (e.g., OBU-based networks, etc.) mayutilize the same Fixed AP. Also for example, the same Fixed AP canprovide a plurality of simultaneous accesses to another single unit(e.g., another Fixed AP, Mobile AP, device, etc.), for example utilizingdifferent channels, different radios, etc.).

Note that a plurality of Fixed APs may be utilized forfault-tolerance/fail-recovery purposes. In an example implementation, aFixed AP and its fail-over AP may both be normally operational (e.g., ina same switch). Also for example, one or more Fixed APs may be placed inthe network at various locations in an inactive or monitoring mode, andready to become operational when needed (e.g., in response to a fault,in response to an emergency services need, in response to a data surge,etc.).

Referring back to FIG. 1, the example Fixed Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. Also, the example Fixed Hotspot AccessNetwork is shown with a wired communication link to one or more BackboneProviders, to the Mobile Hotspot Access Network, to one or more End UserDevices, and to the Environment. The Environment may comprise any of avariety of devices (e.g., in-vehicle networks, devices, and sensors;autonomous vehicle networks, devices, and sensors; maritime (orwatercraft) and port networks, devices, and sensors; generalcontrolled-space networks, devices, and sensors; residential networks,devices, and sensors; disaster recovery & emergency networks, devices,and sensors; military and aircraft networks, devices, and sensors; smartcity networks, devices, and sensors; event (or venue) networks, devices,and sensors; underwater and underground networks, devices, and sensors;agricultural networks, devices, and sensors; tunnel (auto, subway,train, etc.) networks, devices, and sensors; parking networks, devices,and sensors; security and surveillance networks, devices, and sensors;shipping equipment and container networks, devices, and sensors;environmental control or monitoring networks, devices, and sensors;municipal networks, devices, and sensors; waste management networks,devices, and sensors, road maintenance networks, devices, and sensors,traffic management networks, devices, and sensors; advertising networks,devices and sensors; etc.).

The example network 100 of FIG. 1 also comprises a Mobile Hotspot AccessNetwork. Various example characteristics of such a Mobile Hotspot AccessNetwork 300 are shown at FIG. 3. Note that various fixed networkcomponents (e.g., Fixed APs) are also illustrated. The example network300 may, for example, share any or all characteristics with the otherexample methods, systems, networks and/or network components 100, 200,400, 500-570, 600, 700, 800, 900, 1000, and 1100, discussed herein.

The example network 300 comprises a wide variety of Mobile APs (orhotspots) that provide access to user devices, provide for sensor datacollection, provide multi-hop connectivity to other Mobile APs, etc. Forexample, the example network 300 comprises vehicles from differentfleets (e.g., aerial, terrestrial, underground, (under)water, etc.). Forexample, the example network 300 comprises one or more massdistribution/transportation fleets, one or more mass passengertransportation fleets, private/public shared-user fleets, privatevehicles, urban and municipal fleets, maintenance fleets, drones,watercraft (e.g., boats, ships, speedboats, tugboats, barges, etc.),emergency fleets (e.g., police, ambulance, firefighter, etc.), etc.

The example network 300, for example, shows vehicles from differentfleets directly connected and/or mesh connected, for example using sameor different communication technologies. The example network 300 alsoshows fleets simultaneously connected to different Fixed APs, which mayor may not belong to different respective local infrastructureproviders. As a fault-tolerance mechanism, the example network 300 mayfor example comprise the utilization of long-range wirelesscommunication network (e.g., cellular, 3G, 4G, LTE, etc.) in vehicles ifthe local network infrastructure is down or otherwise unavailable. Asame vehicle (e.g., Mobile AP or OBU) can simultaneously provide accessto multiple vehicles, devices, things, etc., for example using a samecommunication technology (e.g., shared channels and/or differentrespective channels thereof) and/or using a different respectivecommunication technology for each. Also for example, a same vehicle canprovide multiple accesses to another vehicle, device, thing, etc., forexample using a same communication technology (e.g., shared channelsand/or different respective channels thereof, and/or using a differentcommunication technology).

Additionally, multiple network elements may be connected together toprovide for fault-tolerance or fail recovery, increased throughput, orto achieve any or a variety of a client's networking needs, many ofexamples of which are provided herein. For example, two Mobile APs (orOBUs) may be installed in a same vehicle, etc.

Referring back to FIG. 1, the example Mobile Hotspot Access Network isshown with a wireless communication link to a backbone provider (e.g.,to one or more Backbone Providers and/or Local InfrastructureProviders), to a Fixed Hotspot Access Network, to one or more End UserDevice, and to the Environment (e.g., to any one of more of the sensorsor systems discussed herein, any other device or machine, etc.). Thoughthe Mobile Hotspot Access Network is not shown having a wired link tothe various other components, there may (at least at times) be such awired link, at least temporarily.

The example network 100 of FIG. 1 also comprises a set of End-UserDevices. Various example end user devices are shown at FIG. 4. Note thatvarious other network components (e.g., Fixed Hotspot Access Networks,Mobile Hotspot Access Network(s), the Backbone/Core, etc.) are alsoillustrated. The example network 400 may, for example, share any or allcharacteristics with the other example methods, systems, networks and/ornetwork components 100, 200, 300, 500-570, 600, 700, 800, 900, 1000, and1100, discussed herein.

The example network 400 shows various mobile networked devices. Suchnetwork devices may comprise end-user devices (e.g., smartphones,tablets, smartwatches, laptop computers, webcams, personal gamingdevices, personal navigation devices, personal media devices, personalcameras, health-monitoring devices, personal location devices,monitoring panels, printers, etc.). Such networked devices may alsocomprise any of a variety of devices operating in the generalenvironment, where such devices might not for example be associated witha particular user (e.g. any or all of the sensor devices discussedherein, vehicle sensors, municipal sensors, fleet sensors road sensors,environmental sensors, security sensors, traffic sensors, waste sensors,meteorological sensors, any of a variety of different types of municipalor enterprise equipment, etc.). Any of such networked devices can beflexibly connected to distinct backbone, fixed hotspot access networks,mobile hotspot access networks, etc., using the same or differentwired/wireless technologies.

A mobile device may, for example, operate as an AP to providesimultaneous access to multiple devices/things, which may then form adhoc networks, interconnecting devices ultimately connected to distinctbackbone networks, fixed hotspot, and/or mobile hotspot access networks.Devices (e.g., any or all of the devices or network nodes discussedherein) may, for example, have redundant technologies to access distinctbackbone, fixed hotspot, and/or mobile hotspot access networks, forexample for fault-tolerance and/or load-balancing purposes (e.g.,utilizing multiple SIM cards, etc.). A device may also, for example,simultaneously access distinct backbone, fixed hotspot access networks,and/or mobile hotspot access networks, belonging to the same provider orto different respective providers. Additionally for example, a devicecan provide multiple accesses to another device/thing (e.g., viadifferent channels, radios, etc.).

Referring back to FIG. 1, the example End-User Devices are shown with awireless communication link to a backbone provider (e.g., to one or moreBackbone Providers and/or Local Infrastructure Providers), to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment. Also for example, the example End-User Devices are shownwith a wired communication link to a backbone provider, to a FixedHotspot Access Network, to a Mobile Hotspot Access Network, and to theEnvironment.

The example network 100 illustrated in FIG. 1 has a flexiblearchitecture that is adaptable at implementation time (e.g., fordifferent use cases) and/or adaptable in real-time, for example asnetwork components enter and leave service. FIGS. 5A-5C illustrate suchflexibility by providing example modes (or configurations). The examplenetworks 500-570 may, for example, share any or all characteristics withthe other example methods, systems, networks and/or network components100, 200, 300, 400, 600, 700, 800, 900, 1000, and 1100, discussedherein. For example and without limitation, any or all of thecommunication links (e.g., wired links, wireless links, etc.) shown inthe example networks 500-570 are generally analogous to similarlypositioned communication links shown in the example network 100 of FIG.1.

For example, various aspects of this disclosure provide communicationnetwork architectures, systems, and methods for supporting a dynamicallyconfigurable communication network comprising a complex array of bothstatic and moving communication nodes (e.g., the Internet of movingthings). For example, a communication network implemented in accordancewith various aspects of the present disclosure may operate in one of aplurality of modalities comprising various fixed nodes, mobile nodes,and/or a combination thereof, which are selectable to yield any of avariety of system goals (e.g., increased throughput, reduced latency andpacket loss, increased availability and robustness of the system, extraredundancy, increased responsiveness, increased security in thetransmission of data and/or control packets, reduced number ofconfiguration changes by incorporating smart thresholds (e.g., change oftechnology, change of certificate, change of IP, etc.), providingconnectivity in dead zones or zones with difficult access, reducing thecosts for maintenance and accessing the equipment forupdating/upgrading, etc.). At least some of such modalities may, forexample, be entirely comprised of fixed-position nodes, at leasttemporarily if not permanently.

For illustrative simplicity, many of the example aspects shown in theexample system or network 100 of FIG. 1 (and other Figures herein) areomitted from FIGS. 5A-5C, but may be present. For example, the Cloud,Internet, and ISP aspects shown in FIG. 1 and in other Figures are notexplicitly shown in FIGS. 5A-5C, but may be present in any of theexample configurations (e.g., as part of the backbone provider networkor coupled thereto, as part of the local infrastructure provider networkor coupled thereto, etc.).

For example, the first example mode 500 is presented as a normalexecution mode, for example a mode (or configuration) in which all ofthe components discussed herein are present. For example, thecommunication system in the first example mode 500 comprises a backboneprovider network, a local infrastructure provider network, a fixedhotspot access network, a mobile hotspot access network, end-userdevices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via a wired link. Note that such a wiredcoupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the first example mode 500 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Also note that in various example configurations,the backbone provider network may also be communicatively coupled to thelocal infrastructure provider network via one or more wireless (ornon-tethered) links.

Though not shown in the first example mode 500 (or any of the examplemodes of FIGS. 5A-5C), one or more servers may be communicativelycoupled to the backbone provider network and/or the local infrastructurenetwork. FIG. 1 provides an example of cloud servers beingcommunicatively coupled to the backbone provider network via theInternet.

As additionally shown in FIG. 5A, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the first example mode 500(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the first example mode 500 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the fixed hotspot access network (or any componentthereof), the mobile hotspot access network (or any component thereof),the end-user devices, and/or environment devices via one or morewireless links. Note that the communication link shown in the firstexample mode 500 of FIG. 5A between the local infrastructure providernetwork and the fixed hotspot access network may be wired and/orwireless.

The fixed hotspot access network is also shown in the first example mode500 to be communicatively coupled to the mobile hotspot access network,the end-user devices, and/or environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Additionally, the mobile hotspot access network is further shownin the first example mode 500 to be communicatively coupled to theend-user devices and/or environment devices via one or more wirelesslinks. Many examples of such wireless coupling are provided herein.Further, the end-user devices are also shown in the first example mode500 to be communicatively coupled to the environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Note that in various example implementations any ofsuch wireless links may instead (or in addition) comprise a wired (ortethered) link.

In the first example mode 500 (e.g., the normal mode), information (ordata) may be communicated between an end-user device and a server (e.g.,a computer system) via the mobile hotspot access network, the fixedhotspot access network, the local infrastructure provider network,and/or the backbone provider network. As will be seen in the variousexample modes presented herein, such communication may flexibly occurbetween an end-user device and a server via any of a variety ofdifferent communication pathways, for example depending on theavailability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an end user device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network).

Similarly, in the first example mode 500 (e.g., the normal mode),information (or data) may be communicated between an environment deviceand a server via the mobile hotspot access network, the fixed hotspotaccess network, the local infrastructure provider network, and/or thebackbone provider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network and/or backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network, thelocal infrastructure provider network, and/or the backbone providernetwork (e.g., skipping the mobile hotspot access network). Also forexample, information communicated between an environment device and aserver may be communicated via the backbone provider network (e.g.,skipping the mobile hotspot access network, fixed hotspot accessnetwork, and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or fixed hotspotaccess network).

As discussed herein, the example networks presented herein areadaptively configurable to operate in any of a variety of differentmodes (or configurations). Such adaptive configuration may occur atinitial installation and/or during subsequent controlled networkevolution (e.g., adding or removing any or all of the network componentsdiscussed herein, expanding or removing network capacity, adding orremoving coverage areas, adding or removing services, etc.). Suchadaptive configuration may also occur in real-time, for example inresponse to real-time changes in network conditions (e.g., networks orcomponents thereof being available or not based on vehicle oruser-device movement, network or component failure, network or componentreplacement or augmentation activity, network overloading, etc.). Thefollowing example modes are presented to illustrate characteristics ofvarious modes in which a communication system may operate in accordancewith various aspects of the present disclosure. The following examplemodes will generally be discussed in relation to the first example mode500 (e.g., the normal execution mode). Note that such example modes aremerely illustrative and not limiting.

The second example mode (or configuration) 510 (e.g., a no backboneavailable mode) may, for example, share any or all characteristics withthe first example mode 500, albeit without the backbone provider networkand communication links therewith. For example, the communication systemin the second example mode 510 comprises a local infrastructure providernetwork, a fixed hotspot access network, a mobile hotspot accessnetwork, end-user devices, and environment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the second example mode 510 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary. Also note thatin various example configurations, the local infrastructure providernetwork may also, at least temporarily, be communicatively coupled tothe mobile hotspot access network (or any component thereof) via one ormore wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the second example mode 510 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links. Note that the communication link(s) shown in thesecond example mode 510 of FIG. 5A between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the second examplemode 510 to be communicatively coupled to the mobile hotspot accessnetwork, the end-user devices, and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Additionally, the mobile hotspot access network isfurther shown in the second example mode 510 to be communicativelycoupled to the end-user devices and/or environment devices via one ormore wireless links. Many examples of such wireless coupling areprovided herein. Further, the end-user devices are also shown in thesecond example mode 510 to be communicatively coupled to the environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Note that in various exampleimplementations any of such wireless links may instead (or in addition)comprise a wired (or tethered) link.

In the second example mode 510 (e.g., the no backbone available mode),information (or data) may be communicated between an end-user device anda server (e.g., a computer, etc.) via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. As will be seen in the various example modes presentedherein, such communication may flexibly occur between an end-user deviceand a server via any of a variety of different communication pathways,for example depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the fixed hotspot access network and/or the local infrastructureprovider network (e.g., skipping the mobile hotspot access network).Also for example, information communicated between an end user deviceand a server may be communicated via the local infrastructure providernetwork (e.g., skipping the mobile hotspot access network and/or fixedhotspot access network).

Similarly, in the second example mode 510 (e.g., the no backboneavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the fixed hotspot access network, and/or the local infrastructureprovider network. Also for example, an environment device maycommunicate with or through an end-user device (e.g., instead of or inaddition to the mobile hotspot access network). As will be seen in thevarious example modes presented herein, such communication may flexiblyoccur between an environment device and a server (e.g., communicativelycoupled to the local infrastructure provider network) via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the fixed hotspot access network and/orthe local infrastructure provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thelocal infrastructure provider network (e.g., skipping the mobile hotspotaccess network and/or fixed hotspot access network).

The second example mode 510 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. Forexample, due to security and/or privacy goals, the second example mode510 may be utilized so that communication access to the public Cloudsystems, the Internet in general, etc., is not allowed. For example, allnetwork control and management functions may be within the localinfrastructure provider network (e.g., wired local network, etc.) and/orthe fixed access point network.

In an example implementation, the communication system might be totallyowned, operated and/or controlled by a local port authority. No extraexpenses associated with cellular connections need be spent. Forexample, cellular connection capability (e.g., in Mobile APs, Fixed APs,end user devices, environment devices, etc.) need not be provided. Notealso that the second example mode 510 may be utilized in a scenario inwhich the backbone provider network is normally available but iscurrently unavailable (e.g., due to server failure, due to communicationlink failure, due to power outage, due to a temporary denial of service,etc.).

The third example mode (or configuration) 520 (e.g., a no localinfrastructure and fixed hotspots available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, the fixed hotspotaccess network, and communication links therewith. For example, thecommunication system in the third example mode 520 comprises a backboneprovider network, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5A, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the third example mode 520 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary. Also note that in various exampleconfigurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5A, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the third example mode 520 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links.

The mobile hotspot access network is further shown in the third examplemode 520 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the third example mode 520 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein. Note that in various example implementations any of suchwireless links may instead (or in addition) comprise a wired (ortethered) link.

In the third example mode 520 (e.g., the no local infrastructure andfixed hotspots available mode), information (or data) may becommunicated between an end-user device and a server (e.g., a computer,etc.) via the mobile hotspot access network and/or the backbone providernetwork. As will be seen in the various example modes presented herein,such communication may flexibly occur between an end-user device and aserver via any of a variety of different communication pathways, forexample depending on the availability of a network, depending onbandwidth utilization goals, depending on communication priority,depending on communication time (or latency) and/or reliabilityconstraints, depending on cost, etc. For example, informationcommunicated between an end user device and a server may be communicatedvia the backbone provider network (e.g., skipping the mobile hotspotaccess network).

Similarly, in the third example mode 520 (e.g., the no localinfrastructure and fixed hotspots available mode), information (or data)may be communicated between an environment device and a server via themobile hotspot access network and/or the backbone provider network. Alsofor example, an environment device may communicate with or through anend-user device (e.g., instead of or in addition to the mobile hotspotaccess network). As will be seen in the various example modes presentedherein, such communication may flexibly occur between an environmentdevice and a server (e.g., communicatively coupled to the backboneprovider network) via any of a variety of different communicationpathways, for example depending on the availability of a network,depending on bandwidth utilization goals, depending on communicationpriority, depending on communication time (or latency) and/orreliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the backbone provider network (e.g., skipping themobile hotspot access network).

In the third example mode 520, all control/management functions may forexample be implemented within the Cloud. For example, since the mobilehotspot access network does not have a communication link via a fixedhotspot access network, the Mobile APs may utilize a direct connection(e.g., a cellular connection) with the backbone provider network (orCloud). If a Mobile AP does not have such capability, the Mobile AP mayalso, for example, utilize data access provided by the end-user devicescommunicatively coupled thereto (e.g., leveraging the data plans of theend-user devices).

The third example mode 520 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the third example mode 520 may be utilized in anearly stage of a larger deployment, for example deployment that willgrow into another mode (e.g., the example first mode 500, example fourthmode 530, etc.) as more communication system equipment is installed.Note also that the third example mode 520 may be utilized in a scenarioin which the local infrastructure provider network and fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The fourth example mode (or configuration) 530 (e.g., a no fixedhotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thefixed hotspot access network and communication links therewith. Forexample, the communication system in the fourth example mode 530comprises a backbone provider network, a local infrastructure providernetwork, a mobile hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), the end-userdevices, and/or environment devices via one or more wired links. Notethat such a wired coupling may be temporary. Also note that in variousexample configurations, the backbone provider network may also, at leasttemporarily, be communicatively coupled to the mobile hotspot accessnetwork (or any component thereof) via one or more wired (or tethered)links.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fourth example mode 530 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fourth example mode 530(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wired links. Note that such a wired coupling may betemporary. Also note that in various example configurations, the localinfrastructure provider network may also, at least temporarily, becommunicatively coupled to the mobile hotspot access network (or anycomponent thereof) via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fourth example mode 530 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), the mobile hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wireless links.

The mobile hotspot access network is further shown in the fourth examplemode 530 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fourth example mode 530 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fourth example mode 530 (e.g., the no fixed hotspots mode),information (or data) may be communicated between an end-user device anda server via the mobile hotspot access network, the local infrastructureprovider network, and/or the backbone provider network. As will be seenin the various example modes presented herein, such communication mayflexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider networkand/or the backbone provider network (e.g., skipping the mobile hotspotaccess network). Also for example, information communicated between anend user device and a server may be communicated via the backboneprovider network (e.g., skipping the mobile hotspot access networkand/or local infrastructure provider network).

Similarly, in the fourth example mode 530 (e.g., the no fixed hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the mobile hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to themobile hotspot access network). As will be seen in the various examplemodes presented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the mobilehotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the mobile hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the mobile hotspot access network and/or backboneprovider network).

In the fourth example mode 530, in an example implementation, some ofthe control/management functions may for example be implemented withinthe local backbone provider network (e.g., within a client premises).For example, communication to the local infrastructure provider may beperformed through the backbone provider network (or Cloud). Note that ina scenario in which there is a direct communication pathway between thelocal infrastructure provider network and the mobile hotspot accessnetwork, such communication pathway may be utilized.

For example, since the mobile hotspot access network does not have acommunication link via a fixed hotspot access network, the Mobile APsmay utilize a direct connection (e.g., a cellular connection) with thebackbone provider network (or Cloud). If a Mobile AP does not have suchcapability, the Mobile AP may also, for example, utilize data accessprovided by the end-user devices communicatively coupled thereto (e.g.,leveraging the data plans of the end-user devices).

The fourth example mode 530 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the fourth example mode 530 may be utilized inan early stage of a larger deployment, for example a deployment thatwill grow into another mode (e.g., the example first mode 500, etc.) asmore communication system equipment is installed. The fourth examplemode 530 may, for example, be utilized in a scenario in which there isno fiber (or other) connection available for Fixed APs (e.g., in amaritime scenario, in a plantation scenario, etc.), or in which a FixedAP is difficult to access or connect. For example, one or more MobileAPs of the mobile hotspot access network may be used as gateways toreach the Cloud. The fourth example mode 530 may also, for example, beutilized when a vehicle fleet and/or the Mobile APs associated therewithare owned by a first entity and the Fixed APs are owned by anotherentity, and there is no present agreement for communication between theMobile APs and the Fixed APs. Note also that the fourth example mode 530may be utilized in a scenario in which the fixed hotspot access networkis normally available but are currently unavailable (e.g., due toequipment failure, due to communication link failure, due to poweroutage, due to a temporary denial of service, etc.).

The fifth example mode (or configuration) 540 (e.g., a no mobilehotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without themobile hotspot access network and communication links therewith. Forexample, the communication system in the fifth example mode 540comprises a backbone provider network, a local infrastructure providernetwork, a fixed hotspot access network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the localinfrastructure provider network (or any component thereof), fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the fifth example mode 540 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Also note that in various exampleconfigurations, the backbone provider network may also becommunicatively coupled to the local infrastructure provider network viaone or more wireless (or non-tethered) links.

As additionally shown in FIG. 5B, and in FIG. 1 in more detail, thelocal infrastructure provider network may be communicatively coupled toany or all of the other elements present in the fifth example mode 540(or configuration) via one or more wired (or tethered) links. Forexample, the local infrastructure provider network may becommunicatively coupled to the backbone provider network (or anycomponent thereof), fixed hotspot access network (or any componentthereof), the end-user devices, and/or environment devices via one ormore wired links. Note that such a wired coupling may be temporary. Alsonote that in various example configurations, the local infrastructureprovider network may also, at least temporarily, be communicativelycoupled to the mobile hotspot access network (or any component thereof)via one or more wired (or tethered) links.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the fifth example mode 540 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the backbone provider network, the fixedhotspot access network (or any component thereof), the end-user devices,and/or environment devices via one or more wireless links. Note that thecommunication link(s) shown in the fifth example mode 540 of FIG. 5Bbetween the local infrastructure provider network and the fixed hotspotaccess network may be wired and/or wireless.

The fixed hotspot access network is also shown in the fifth example mode540 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Further, the end-userdevices are also shown in the fifth example mode 540 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the fifth example mode 540 (e.g., the no mobile hotspots availablemode), information (or data) may be communicated between an end-userdevice and a server via the fixed hotspot access network, the localinfrastructure provider network, and/or the backbone provider network.As will be seen in the various example modes presented herein, suchcommunication may flexibly occur between an end-user device and a servervia any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc. For example, information communicated between anend user device and a server may be communicated via the localinfrastructure provider network, and/or the backbone provider network(e.g., skipping the fixed hotspot access network). Also for example,information communicated between an end user device and a server may becommunicated via the backbone provider network (e.g., skipping the fixedhotspot access network and/or local infrastructure provider network).

Similarly, in the fifth example mode 540 (e.g., the no mobile hotspotsavailable mode), information (or data) may be communicated between anenvironment device and a server via the fixed hotspot access network,the local infrastructure provider network, and/or the backbone providernetwork. Also for example, an environment device may communicate with orthrough an end-user device (e.g., instead of or in addition to the fixedhotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network and/or backbone provider network)via any of a variety of different communication pathways, for exampledepending on the availability of a network, depending on bandwidthutilization goals, depending on communication priority, depending oncommunication time (or latency) and/or reliability constraints,depending on cost, etc.

For example, information communicated between an environment device anda server may be communicated via the local infrastructure providernetwork and/or the backbone provider network (e.g., skipping the fixedhotspot access network). Also for example, information communicatedbetween an environment device and a server may be communicated via thebackbone provider network (e.g., skipping the fixed hotspot accessnetwork and/or local infrastructure provider network). Additionally forexample, information communicated between an environment device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network and/or the backboneprovider network).

In the fifth example mode 540, in an example implementation, theend-user devices and environment devices may communicate directly toFixed APs (e.g., utilizing Ethernet, Wi-Fi, etc.). Also for example, theend-user devices and/or environment devices may communicate directlywith the backbone provider network (e.g., utilizing cellularconnections, etc.).

The fifth example mode 540 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation in which end-user devices and/or environmentdevices may communicate directly with Fixed APs, such communication maybe utilized instead of Mobile AP communication. For example, the fixedhotspot access network might provide coverage for all desired areas.

Note also that the fifth example mode 540 may be utilized in a scenarioin which the fixed hotspot access network is normally available but iscurrently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The sixth example mode (or configuration) 550 (e.g., the no fixed/mobilehotspots and local infrastructure available mode) may, for example,share any or all characteristics with the first example mode 500, albeitwithout the local infrastructure provider network, fixed hotspot accessnetwork, mobile hotspot access network, and communication linkstherewith. For example, the communication system in the sixth examplemode 550 comprises a backbone provider network, end-user devices, andenvironment devices.

As shown in FIG. 5B, and in FIG. 1 in more detail, the backbone providernetwork may be communicatively coupled to any or all of the otherelements present in the sixth example mode 550 (or configuration) viaone or more wired (or tethered) links. For example, the backboneprovider network may be communicatively coupled to the end-user devicesand/or environment devices via one or more wired links. Note that such awired coupling may be temporary.

Also shown in FIG. 5B, and in FIG. 1 in more detail, the backboneprovider network may be communicatively coupled to any or all of theother elements present in the sixth example mode 550 (or configuration)via one or more wireless links (e.g., RF link, non-tethered opticallink, etc.). For example, the backbone provider network may becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links.

The end-user devices are also shown in the sixth example mode 550 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the sixth example mode 550 (e.g., the no fixed/mobile hotspots andlocal infrastructure available mode), information (or data) may becommunicated between an end-user device and a server via the backboneprovider network. Similarly, in the sixth example mode 550 (e.g., the nofixed/mobile hotspots and local infrastructure mode), information (ordata) may be communicated between an environment device and a server viathe backbone provider network. Also for example, an environment devicemay communicate with or through an end-user device (e.g., instead of orin addition to the mobile hotspot access network).

The sixth example mode 550 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, for example in which an end-user has not yetsubscribed to the communication system, the end-user device maysubscribe to the system through a Cloud application and by communicatingdirectly with the backbone provider network (e.g., via cellular link,etc.). The sixth example mode 550 may also, for example, be utilized inrural areas in which Mobile AP presence is sparse, Fixed AP installationis difficult or impractical, etc.

Note also that the sixth example mode 550 may be utilized in a scenarioin which the infrastructure provider network, fixed hotspot accessnetwork, and/or mobile hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

The seventh example mode (or configuration) 560 (e.g., the no backboneand mobile hotspots available mode) may, for example, share any or allcharacteristics with the first example mode 500, albeit without thebackbone provider network, mobile hotspot access network, andcommunication links therewith. For example, the communication system inthe seventh example mode 560 comprises a local infrastructure providernetwork, fixed hotspot access network, end-user devices, and environmentdevices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the localinfrastructure provider network may be communicatively coupled to any orall of the other elements present in the seventh example mode 560 (orconfiguration) via one or more wired (or tethered) links. For example,the local infrastructure provider network may be communicatively coupledto the fixed hotspot access network (or any component thereof), theend-user devices, and/or environment devices via one or more wiredlinks. Note that such a wired coupling may be temporary.

Also, though not explicitly shown, the local infrastructure providernetwork may be communicatively coupled to any or all of the otherelements present in the seventh example mode 560 (or configuration) viaone or more wireless links (e.g., RF link, non-tethered optical link,etc.). For example, the local infrastructure provider network may becommunicatively coupled to the fixed hotspot access network (or anycomponent thereof), the end-user devices, and/or environment devices viaone or more wireless links. Note that the communication link shown inthe seventh example mode 560 of FIG. 5C between the local infrastructureprovider network and the fixed hotspot access network may be wiredand/or wireless.

The fixed hotspot access network is also shown in the seventh examplemode 560 to be communicatively coupled to the end-user devices and/orenvironment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein. Additionally, the end-userdevices are also shown in the seventh example mode 560 to becommunicatively coupled to the environment devices via one or morewireless links. Many examples of such wireless coupling are providedherein.

In the seventh example mode 560 (e.g., the no backbone and mobilehotspots available mode), information (or data) may be communicatedbetween an end-user device and a server via the fixed hotspot accessnetwork and/or the local infrastructure provider network. As will beseen in the various example modes presented herein, such communicationmay flexibly occur between an end-user device and a server via any of avariety of different communication pathways, for example depending onthe availability of a network, depending on bandwidth utilization goals,depending on communication priority, depending on communication time (orlatency) and/or reliability constraints, depending on cost, etc. Forexample, information communicated between an end user device and aserver may be communicated via the local infrastructure provider network(e.g., skipping the fixed hotspot access network).

Similarly, in the seventh example mode 560 (e.g., the no backbone andmobile hotspots available mode), information (or data) may becommunicated between an environment device and a server via the fixedhotspot access network and/or the local infrastructure provider network.Also for example, an environment device may communicate with or throughan end-user device (e.g., instead of or in addition to the mobilehotspot access network). As will be seen in the various example modespresented herein, such communication may flexibly occur between anenvironment device and a server (e.g., communicatively coupled to thelocal infrastructure provider network) via any of a variety of differentcommunication pathways, for example depending on the availability of anetwork, depending on bandwidth utilization goals, depending oncommunication priority, depending on communication time (or latency)and/or reliability constraints, depending on cost, etc. For example,information communicated between an environment device and a server maybe communicated via the local infrastructure provider network (e.g.,skipping the fixed hotspot access network).

The seventh example mode 560 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample controlled space implementation, Cloud access might not beprovided (e.g., for security reasons, privacy reasons, etc.), and full(or sufficient) coverage of the coverage area is provided by the fixedhotspot access network, and thus the mobile hotspot access network isnot needed. For example, the end-user devices and environment devicesmay communicate directly (e.g., via Ethernet, Wi-Fi, etc.) with theFixed APs

Note also that the seventh example mode 560 may be utilized in ascenario in which the backbone provider network and/or fixed hotspotaccess network are normally available but are currently unavailable(e.g., due to equipment failure, due to communication link failure, dueto power outage, due to a temporary denial of service, etc.).

The eighth example mode (or configuration) 570 (e.g., the no backbone,fixed hotspots, and local infrastructure available mode) may, forexample, share any or all characteristics with the first example mode500, albeit without the backbone provider network, local infrastructureprovider network, fixed hotspot access network, and communication linkstherewith. For example, the communication system in the eighth examplemode 570 comprises a mobile hotspot access network, end-user devices,and environment devices.

As shown in FIG. 5C, and in FIG. 1 in more detail, the mobile hotspotaccess network is shown in the eighth example mode 570 to becommunicatively coupled to the end-user devices and/or environmentdevices via one or more wireless links. Many examples of such wirelesscoupling are provided herein. Further, the end-user devices are alsoshown in the eighth example mode 570 to be communicatively coupled tothe environment devices via one or more wireless links. Many examples ofsuch wireless coupling are provided herein.

In the eighth example mode 570 (e.g., the no backbone, fixed hotspots,and local infrastructure available mode), information (or data) mightnot (at least currently) be communicated between an end-user device anda server (e.g., a coupled to the backbone provider network, localinfrastructure provider network, etc.). Similarly, information (or data)might not (at least currently) be communicated between an environmentdevice and a server (e.g., a coupled to the backbone provider network,local infrastructure provider network, etc.). Note that the environmentdevice may communicate with or through an end-user device (e.g., insteadof or in addition to the mobile hotspot access network).

The eighth example mode 570 may be utilized for any of a variety ofreasons, non-limiting examples of which are provided herein. In anexample implementation, the eighth example mode 570 may be utilized forgathering and/or serving data (e.g., in a delay-tolerant networkingscenario), providing peer-to-peer communication through the mobilehotspot access network (e.g., between clients of a single Mobile AP,between clients of respective different Mobile APs, etc.), etc. Inanother example scenario, the eighth example mode 570 may be utilized ina scenario in which vehicle-to-vehicle communications are prioritizedabove vehicle-to-infrastructure communications. In yet another examplescenario, the eighth example mode 570 may be utilized in a scenario inwhich all infrastructure access is lost (e.g., in tunnels, parkinggarages, etc.).

Note also that the eighth example mode 570 may be utilized in a scenarioin which the backbone provider network, local infrastructure providernetwork, and/or fixed hotspot access network are normally available butare currently unavailable (e.g., due to equipment failure, due tocommunication link failure, due to power outage, due to a temporarydenial of service, etc.).

As shown and discussed herein, it is beneficial to have a genericplatform that allows multi-mode communications of multiple users ormachines within different environments, using multiple devices withmultiple technologies, connected to multiple moving/static things withmultiple technologies, forming wireless (mesh) hotspot networks overdifferent environments, connected to multiple wired/wirelessinfrastructure/network backbone providers, ultimately connected to theInternet, Cloud or private network infrastructure.

FIG. 6 shows yet another block diagram of an example networkconfiguration, in accordance with various aspects of the presentdisclosure. The example network 600 may, for example, share any or allcharacteristics with the other example methods, systems, networks and/ornetwork components 100, 200, 300, 400, 500-570, 700, 800, 900, 1000, and1100, discussed herein. Notably, the example network 600 shows aplurality of Mobile APs (or OBUs), each communicatively coupled to aFixed AP (or RSU), where each Mobile AP may provide network access to avehicle network (e.g., comprising other vehicles or vehicle networks,user devices, sensor devices, etc.).

In accordance with various aspects of the present disclosure, systemsand methods are provided that manage a vehicle communication network,for example in accordance with the location of nodes and end devices, ina way that provides for stable TCP/IP Internet access, among otherthings. For example, an end user may be provided with a clean and stableWi-Fi Internet connection that may appear to the end user to be the sameas the Wi-Fi Internet connection at the user's home, user's workplace,fixed public Wi-Fi hotspots, etc. For example, for a user utilizing acommunication network as described herein, a TCP session may stayactive, downloads may process normally, calls may proceed withoutinterruption, etc. As discussed herein, a vehicle communication networkin accordance with various aspects of this disclosure may be applied asa transport layer for regular Internet traffic and/or for privatenetwork traffic (e.g., extending the access of customer private LANsfrom the wired network to vehicles and users around them, etc.).

In accordance with an example network implementation, although a usermight be always connected to a single Wi-Fi AP of a vehicle, the vehicle(or the access point thereof, for example an OBU) is moving betweenmultiple access points (e.g., Fixed APs, other Mobile APs, cellular basestations, fixed Wi-Fi hotspots, etc.). For example, mobility managementimplemented in accordance with various aspects of the present disclosuresupports the mobility of each vehicle and its users across differentcommunication technologies (e.g., 802.11p, cellular, Wi-Fi, etc.) as theMobile APs migrate among Fixed APs (and/or Mobile APs, Wi-Fi Hotspots,cellular base stations, etc.) and/or as users migrate between Mobile APs(and/or Fixed APs, Wi-Fi Hotspots, cellular base stations, etc.).

In accordance with various aspects of the present disclosure, a mobilitycontroller (MC), which may also be referred to as an LMA or NetworkController, may monitor the location (e.g., network location, etc.) ofvarious nodes (e.g., Mobile APs, etc.) and/or the location of end usersconnected through them. The mobility controller (MC) may, for example,provide seamless handovers (e.g., maintaining communication sessioncontinuity) between different access points and/or differenttechnologies with low link latency and low handover times.

The architecture provided herein is scalable, for example takingadvantage of redundant elements and/or functionality to provideload-balancing of control and/or data communication functionality, aswell as to decrease failure probability. Various aspects of the presentdisclosure also provide for decreased control signaling (e.g., in amountand/or frequency), which reduces the control overhead and reduces thesize of control tables and tunneling, for example both in backendservers and in APs (e.g., Fixed APs and/or Mobile APs).

Additionally, a communication network (or components thereof) inaccordance with various aspects of this disclosure may comprise theability to interact with mobile devices in order to control some or allof their connection choices and/or to leverage their controlfunctionality. For example, in an example implementation, a mobileapplication can run in the background, managing the available networksand/or nodes thereof and selecting the one that best fits, and thentriggering a handoff to the selected network (or node thereof) beforebreakdown of the current connection.

The communication network (or components thereof) is also configurable,according to the infrastructure requirements and/or mobility needs ofeach client, etc. For example, the communication network (or componentsthereof) may comprise the capability to support different Layer 2 (L2)or Layer 3 (L3) implementations, or combinations thereof, as well asIPv4/IPv6 traffic.

At various times during operation of the vehicle network as presentedherein, the resources of the vehicle network may be unutilized orunderutilized. For example, the resources of the vehicle network may beselected such that acceptable performance is provided in a worst casescenario. An unfortunate side affect of such network design is thatresources are purchased and maintained but are often underutilized. Anopportunity thus exists to recuperate at least a portion of theinvestment by providing a system and method that provides for theutilization of such underutilized resources. Such resources may, forexample, comprise stationary and/or moving processing resources, memoryresources, general data gathering/storing/processing resources, sensordata gathering/storing/processing resources, communication resources,energy resources, etc. Various aspects of this disclosure leverage theexcess capacity (e.g., computational or processing capacity, dataacquisition and/or processing capacity, memory capacity, energycapacity, etc.) to offer (or provide) the vehicular network as a serviceto developers and systems that want to run their applications andservices in a distributed fashion. For example, the systems and methodsdiscussed herein may also provide for the reduction of communicationnetwork traffic by offloading the computation from the Cloud to the edgeof the network, where for example the data is available at a lower costand lower latency, and where multiple processors (e.g., mobileprocessors, access point processors, etc.) may acquire and/or processthe data in parallel. Additionally, the flexibility and power of avehicle communication system implemented in accordance with variousaspects of the present disclosure may result in relatively large amountsof data (e.g., client data, sensor data, vehicle data, etc.)communicated through communication links with finite bandwidth,resulting in network congestion, latency, unavailability, etc. A systemand/or method implemented in accordance with various aspects of thepresent disclosure may address at least a portion of suchbandwidth-related issues. For example, at least a portion of theapplication processing may be pushed down to the edge nodes (e.g.,Mobile APs, Fixed APs, etc.), where such processing may, for example,analyze and/or summarize collected data or other information (e.g.,summarizing measurement results, providing data analysis results withless or no raw data, performing various types of compression orfiltering, etc.). The results of such analysis and/or summarizing and/orprocessing may be communicated through the network instead of therelatively larger amount of raw data.

It should be noted that although various systems and methods may existfor the time-sharing of various computational and/or memory resources,such systems and methods fail in the context of the vehiclecommunication network. As a non-limiting example, due to the mobilenature of various resources and/or data sources, and/or the requirementto provide services to mobile infrastructure and/or client nodes,traditional ways of utilizing underutilized resources are inadequate,for example failing to consider the effects that mobility has on anavailable resource. For example, based at least in part on mobility of aresource, the resource may only be available (or may only be availablefor a particular desired purpose) for a particular time window, outsideof which an alternate resource may be available for utilization. Forexample, a particular mobile access point may be within wirelesscommunication range of a particular stationary sensor as a data sourceduring a particular time window, outside of which the particular mobileaccess point might not have communicative access to the particularstationary sensor. Also for example, as a particular mobile access pointenters and exits particular geographical regions with particularrespective amounts of utilization of the mobile access point's networkaccess services (e.g., mobile Internet access, etc.), the availabilityof various resources of the particular mobile access point will change.In other words, a resource of a mobile access point that isunderutilized at a first location may be maximally utilized a fewmoments later, and return to an underutilized status a few momentslater. Traditional methods of resource allocation and utilization areunable to perform adequately in such circumstances.

Also, systems and methods implemented in accordance with various aspectsof the present disclosure may, for example, provide (or define) adevelopment environment that defines how developers interact (e.g., withthe system, with each other, etc.) and develop applications to bedistributed (e.g., adaptively distributed, etc.) in the MobileComputation Nodes (MCNs) in the Internet of Moving Things (IMT) usingthe Vehicle Network As A Service (VNAAS).

Also, systems and methods implemented in accordance with various aspectsof the present disclosure may, for example, provide for the testing andvalidation of applications before such applications are distributed tothe MCNs. Though such testing and validation may, for example, beimplemented during the development of applications (e.g., to provideearly warning for developers or system administrators, etc.), finaltesting and validation may also be performed to ensure the operationalintegrity of the system (e.g., of the vehicle communication system,infrastructure, Cloud servers, etc.).

Further, systems and methods implemented in accordance with variousaspects of the present disclosure may, for example, define fundamentalstructures (e.g., objects, methods, procedures, functions, executinghierarchy, standard APIs available for utilization, data structures,messages, etc.) for the applications to be distributed and used in aVNAAS scenario. Such fundamental structures may, for example, beprovided to the developers in the development environment (e.g., in anIntegrated Development Environment (IDE), Computer Assisted SoftwareEngineering (CASE) tools, etc.) to assist the developers in developingapplications that are compatible with the system.

Additionally, systems and methods implemented in accordance with variousaspects of the present disclosure may, for example, determine (ordefine) how multiple applications (e.g., related or unrelatedapplications) will be scheduled and distributed in the MCNs, for exampleutilizing a Cloud-based VNAAS Gatekeeper (CVG). For example, suchscheduling (or mapping) may include determining how the CVG will map theapplication requirements with the local resources to be utilized in theMCNs.

Further, systems and methods implemented in accordance with variousaspects of the present disclosure may, for example, assess the existing(and/or anticipated) excess and underutilized capacity in the MCNs. Suchassessment may, for example, be performed continually, periodically,etc. The results of such assessment may, for example, be utilized in thescheduling and distribution of applications, in billing for resourceutilization, etc.

Still further, systems and methods implemented in accordance withvarious aspects of the present disclosure may, for example, measure theexecution of the applications and/or the resources utilized by theapplications executing on the MCNs. For example, the CVG may collectdata and logging produced by the several applications running on theMCNs. The results of such measuring may, for example, be utilized forbilling and accounting purposes, as feedback for the adaptation of themanner in which applications are scheduled on the MCNs, etc.

Various aspects of the present disclosure will now be presented byreferring to example drawings of system and network components andmethods, of application life cycle diagrams, etc.

Turning to FIG. 7, such figure shows a block diagram of an examplecommunication network, in accordance with various aspects of the presentdisclosure. The example communication network 700 (or system) orcomponents thereof may share any or all characteristics with the otherexample methods, systems, networks and/or network components 100, 200,300, 400, 500-570, 600, 800, 900, 1000, 1000, and 1100, discussedherein.

One or more developers 705 may, for example, develop (e.g., design,code, test, etc.) an application in a familiar development environment,which may for example be provided by a CVG 710 based in the Cloud 711(e.g., the Internet, etc.). Note that the CVG 710 may be alsoimplemented on a proprietary system, access to which may be tightlyregulated. The CVG 710 may, for example, provide a development interfaceby which a developer 705 may define data, networking, and resourcerequirements, etc. (e.g., of one or more MCNs, general vehiclenetworking environment, any of the vehicle network nodes discussedherein, etc.) that would be executed in a number of MCNs (e.g., MAPs,FAPs, vehicles, etc.) that are part of the vehicle network. Suchexecution may, for example, utilize excess resources (e.g., resourcesthat are not utilized, underutilized, etc.) of the nodes of the vehiclenetwork. As discussed herein, such resources may comprise processor (orcomputation) resources, memory resources, communication resources, dataaccess resources, sensor resources, etc. For example, an excess resourcemay include a communication link (e.g., a channel, a portion of achannel, etc.) that will be available during a particular time windowbetween a MAP and a sensor, and another excess resource may include aprocessor of the MAP that may analyze the data from the sensor anddevelop a summary of the analyzed data, and a further excess resourcemay include a communication circuit of the MAP that may communicate thesummary to a cloud server via the vehicle communication network, and astill further excess resource may be memory space that may be availableat least temporarily to carry data until such data can be offloaded.

In the example network 700, the CVG 710 may be communicatively coupledto Fixed APs 731, 732, and 733, Mobile APs 741, 742, and 743, networkcomponents 750 of a vehicle (e.g., cameras, microphones, scales, weathersensors, user smart phones, user computers, autonomous vehicle controlsystem components, on-board diagnostic components, etc.), etc., througha backbone infrastructure, Network Controllers (NCs) of the vehiclenetwork, etc. As discussed herein, an MCN may include a Fixed AP, aMobile AP, another device (e.g., a sensor device, a client computingdevice, etc.) communicatively coupled to a Fixed AP and/or Mobile AP,etc., of the vehicle network. As shown in FIG. 7, the CVG 710 may mapapplications to the MCNs (e.g., Fixed APs 731, 732, and 733; Mobile APs741, 742, and 743; network components 750; etc.) and otherwise scheduleand control their execution. Also, as shown in FIG. 7, the various FixedAPs 731, 732, and 733 and Mobile APs 741, 742, and 743 may communicatewith each other, providing communication pathways for the applicationsto communicate with each other.

For example, in an example scenario, the CVG 710 may map applications(or portions thereof) to an access point or other MCN based, at least inpart, on location of the access point or other MCN. For example, aparticular MCN (or group thereof) may be located (or anticipated to belocated) within communication range of a sensor at a particularlocation, a particular MCN (or group thereof) may be located (oranticipated to be located) within communication range of a particularintersection, a particular MCN (or group thereof) may be located on aparticular street, a particular MCN (or group thereof) may be withincommunication range (or anticipated to be within communication range) ofa particular venue, etc. Note that the location of the MCN (and/or aresource communicatively coupled to the MCN) may change over time. Forexample, the MCN may have a trajectory, and such trajectory may impactthe ability of the MCN to perform a desired function for an application.In an example scenario involving an application that collects andprocesses data from a particular sensor in the field at a particularlocation, the CVG may map the application to a first set of one or moreMCNs (e.g., stationary and/or mobile MCNs) that are anticipated to benear the particular location during a first time window, and map theapplication to a second set of one or more MCNs (e.g., stationary and/ormobile MCNs) that are anticipated to be near the particular locationduring a second time window, etc. Note that the application mapping maythen, for example, be adjusted based on real-time location information,for example to accommodate circumstances where one or more MCNs are notwhere they were anticipated to be, or otherwise are unable to performthe mapped operations.

Turning next to FIG. 8, such figure shows a block diagram of an exampleCloud-based Vehicle-Network-As-A-Service (VNAAS) Gatekeeper (or CVG) andnetwork, in accordance with various aspects of the present disclosure.The example communication network 800 (or system) or components thereofmay share any or all characteristics with the other example methods,systems, networks and/or network components 100, 200, 300, 400, 500-570,600, 700, 900, 1000, and 1100, discussed herein.

The Cloud-based VNAAS Gatekeeper (CVG) 810 may, for example, generallyoperate as the main coordinator for the developing, distributing, andglobally controlling execution of applications, etc. For example, theCVG 810 may provide an environment for developers 805 to developapplications and to upload developed applications to the system. The CVG810 may also, for example, manage the mapping of the applications toavailable resources (e.g., underutilized MCN resources, etc.) of thevehicle network. The CVG 810 may also, for example, manage and performthe distribution of applications to the MCNs 820. Also for example, theCVG 810 may control or manage the execution of the applications at theMCNs 820. Additionally, for example, the CVG 810 may monitor theexecution of the applications at the MCNs 820, for example for billingpurposes, to identify and handle applications that are not performing inan allowed manner or otherwise harming the system, to utilize asfeedback to the selected mapping, etc.

The example CVG 810 of FIG. 8 may, for example, include variousfunctional modules (e.g., software or firmware code implemented by oneor more processors thereof, etc.) that operate to perform the variousCVG functionalities discussed herein.

For example, the example CVG 810 may include an Application DevelopmentManager (ADM) 812, or ADM module, that operates to provide theapplication development environment discussed herein, for example,providing Computer Assisted Software Engineering (CASE) tools and/or anIntegrated Development Environment (IDE) to developers, for example,providing pre-defined, tested, and approved application structures(e.g., objects, attributes, methods, functions, procedures, datastructures, data definitions, message structures, etc.) for theefficient development of applications that meet the design criteria setforth for the vehicle network.

Also for example, the example CVG 810 may include an Application UploadManager (AUM) 813, or AUM Module, that operates to receive applicationsfrom developers 805. The AUM 813 may, for example, perform any number ofchecks and validations on the received applications to ensure that theuploaded applications match the specifications of the system, match theprogramming language(s) and/or operating systems in use, etc. Note that,as discussed herein, the ADM 813 may provide one or more CASE tools,with pre-developed and pre-approved fundamental structures (or buildingblocks) that may be used by developers 805 during development to avoidvarious validation issues that may be flagged by the AUM 813 during thevalidation process.

In an example implementation, the CVG 810 may provide a robust emulation(or simulation) environment (e.g., emulating the operation of any or allof the nodes of the vehicle communication network, emulating expectedoperating environments, etc.) in which developers 805 may interfacetheir application code with emulated (or simulated) vehicle networknodes (e.g., potential MCNs), for example utilizing the exact interfaceswith which the application code would interface with real-world vehiclenetwork nodes. In an example implementation, the CVG 810 may alsoutilize various simulated scenarios in a test suite as part of thevalidation procedure.

Additionally for example, the CVG 810 may include a Mapper 815 thatoperates to receive the validated application code from the AUM 813, andextract (or segment or separate or identify) the code that will bedistributed and executed in one or more of the MCNs 820 and the codethat will be executed in the CVG 810 (or other centralized node, forexample a network controller, etc.) during and/or after the execution ofthe application (or portions thereof) at the MCN(s). For example,application code may include a central (or master) application, whichmay for example be run at a cloud server or network controller or otherdevice(s), that interfaces with (e.g., controls, directs,requests/receives data from, etc.) child (or slave) applications, whichmay for example be executed at or near the vehicle communication networkedge nodes (e.g., Mobile APs, Fixed APs, etc.). The Mapper 815 may also,for example, allocate (or communicate) the global and specific rules todistribute computation in the several MCNs 820.

Note that an application (or portion thereof) need not be developed torun only on a particular network node (e.g., on a CVG 810, on an MCN820, etc.). For example, in an example implementation, an application(or portion thereof) may be developed that may adaptively be executed atthe Cloud server level (e.g., at the CVG 810 or other server) or at theMCN 820 level. In such an implementation, the Mapper 815 may flexiblydetermine (e.g., based on amount of network traffic, based on profileparameters of the application developer, based on cost, etc.) whether tomap the application (or portion thereof) to one or more MCNs 820 orwhether to execute the application (or portion thereof) at the Cloudlevel, for example at a CVG 810.

For example, the Mapper 815 may operate to map the MCN portions of theapplication(s) to underutilized resources of one or more MCNs 820. In anexample scenario, the Mapper 820 may identify a subset of the availableMCNs for executing an application, for example, mapping an applicationto a set of MCNs (e.g., to a set of MCNs having the most respectiveunderutilized resources, to a set of MCNs located in and/or anticipatedto be located in a particular area and having underutilized resources,etc.) until a resource utilization goal is met. For example, the Mapper815 may identify a target amount of data acquisition and/or processingdesired (e.g., minimum target, optimal target, etc.) for an application,and allocate enough MCNs 820 (or underutilized resources thereof) tomeet the target amount.

Note that the Mapper 815 may adjust the allocation of resources duringexecution of the applications by the MCNs 820, for example due tochanging amount of underutilized resources in the MCNs 820, etc. Forexample, in an example scenario in which an Mobile AP acting as an MCNenters an area that demands the utilization of most or all of the MobileAP's resources to fulfill its primary purpose as a mobile communicationnode, the Mapper 815 may identify this situation and move applicationprocessing from the Mobile AP to another Mobile AP that presently hasunderutilized resources. The Mapper 815 may, for example, receiveinformation from the Mobile AP (or a central network controller, etc.)indicating that the Mobile AP's resources are (or are anticipated to be)mostly utilized for functionality of primary importance to the Mobile AP(e.g., functionality directly associated with operation of the vehiclecommunication network, emergency functionality, safety functionality,etc.). The MCN 820, in this scenario, may periodically send resourceutilization status messages (e.g., including information identifyingcurrent respective resource utilization for one or more resourcesthereof, anticipated respective resource utilization for one or moreresources thereof, etc.) to the CVG 810, may send such status messagestriggered by one or more resource utilization thresholds, may send suchstatus messages to the CVG 810 synchronously upon request from the CVG810, may send such status messages asynchronously, etc. For example, anMCN 820 may message the CVG 810 upon determining that a previouslyallocated resource is now (or anticipated to be) over-utilized. The MCN820 may, for example, make such a determination based on presentoperating conditions and/or on historical utilization (e.g., as afunction of location, time, day, etc.).

Note that the Mapper 815 may map applications to MCNs 820 based on anyof a variety of considerations. For example, the Mapper 815 may developa distribution function (e.g., a function of time, etc.) that governsthe distribution of one or more applications to the MCNs 810 and/or theexecution of the one or more distributed applications. For example, theMapper 815 may map applications to MCNs 820 based on percentage ofavailable or underutilized resources of the MCNs 820 (e.g., currentand/or anticipated percentage), based on geographical location (and/orvelocity) of the MCNs 820, based on energy-remaining levels of the MCNs820, based on current and/or predicted direction of travel of the MCNs820 (e.g., heading toward or away from busy areas, etc.), based on fleetidentity, based on time-of-day, based on type-of-day, based on day-ofweek, based on historical resource utilization, etc. Any or all of suchinformation may be provided by the MCNs 820 in real-time, may beprovided by a central vehicle network controller, a combination thereof,etc.). For example, in an example scenario, the Mapper 815 may calculate(e.g., based on actual and/or anticipated MCN 820 location and/ortrajectory information) an expected amount of time that an MCN 820 maybe within communication range of a sensor of interest, and base themapping (or distribution) of application execution to the MCN 820 basedat least in part on the expected amount of time. Also for example, in anexample scenario, the Mapper 815 may (e.g., based on current time (e.g.,time-of-day, day-of-week, etc.) and historical resource utilization foran MCN 820 in a particular geographical area) anticipate that the MCN820 is about to have a relatively high amount of available resources ora particular resource of interest, and schedule an application for theMCN 820 during a time period that coincides with a window of anticipatedhigh availability. Additionally, for example, in an example scenario inwhich the application was defined to obtain information from a sourceover a time period that for various reasons (e.g., location and/ortrajectory reasons, resource availability reasons, etc.) is notserviceable by a particular MCN 820 or group thereof, the Mapper 815 maysequentially map the application for execution by different sets of oneof more MCNs 820 throughout the time period. For example, the Mapper 815may, during a first portion of an overall requested time period, map asensor data acquisition and/or analysis application to a first set ofone or more MCNs 820 that are anticipated to be in a geographical areaduring the first portion of the time period, and during a second portionof the overall requested time period, map the sensor data acquisitionapplication to a second set of one or more MCNs 820 that are anticipatedto be in the geographical area during the second portion of the timeperiod. Note that the first and second sets may comprise at leastpartial overlapping membership, but need not. Note also, that either ofthe first and second sets may comprise mobile and/or stationaryresources.

The example CVG 810 also comprises a Billing Module 816 that operates tocalculate, track, and measure the execution credits calculated based ona configurable cost-function. The Billing Module 816 may, for example,received data and logging information, processing time information,communication bandwidth information, memory utilization memory, etc.from the MCNs 820. The Billing Module 816 may then, for example, executea cost function to process such information to identify a monetary cost(or other cost indicator) associated with an application. For example,the Billing Module 816 may accumulate respective costs for execution ofan application from each of a plurality of MCNs 820 to identify a totalcost. Note that such a cost function may be adaptable, for example basedon customer priority, based on resource availability, based ontime-of-day, based on day-of-week, etc.

The example CVG 810 additionally comprises a Scheduler 817 (or SchedulerModule) that operates to distribute the applications to the several MCNs820 based on the distribution function provided by the Mapper 815. TheScheduler 817 may, for example, open and/or maintain the communicationlinks between the CVG 810 and the MCNs 820 to implement applicationdownloading, to implement application execution control, etc.

The example CVG 810 further comprises a Harvester 818 (or HarvesterModule) that operates to collect information (or data) sent by the MCNs820. Such information (or data) may, for example, compriseapplication-specific data (e.g., collected sensor data, results of dataprocessing, login information, information indicating an amount ofresource utilization, etc.), billing logging information, feedbackinformation related to the performance of the present mapping, etc. Notethat the Harvester 818 may passively collect the information (or data)sent by the MCNs 820 (e.g., in an asynchronous manner) and/or mayactively solicit (or request) the information (or data) (e.g., in asynchronous manner), for example periodically, when a need for mappingor remapping an application arises, when a fault condition or potentialfault condition is detected, etc.

Turning next to FIG. 9, such figure shows a block diagram of an exampleMobile Computing Node (MCN) and network, in accordance with variousaspects of the present disclosure. The example communication network 900(or system) or components thereof may share any or all characteristicswith the other example methods, systems, networks and/or networkcomponents 100, 200, 300, 400, 500-570, 600, 700, 800, 1000, and 1100,discussed herein.

A Mobile Computing Node (MCN) 910 may, for example, be any of a varietyof elements of nodes of a vehicle network or an Internet of MovingThings (IMT) implementation. For example, an MCN 910 may comprise aMobile AP (or MAP), a Fixed AP (or FAP), a Network Controller (or NC), aportion of a network local to a vehicle (e.g., an autonomous vehiclecontrol system, on-board diagnostic (OBD) system, etc.), etc. The MCN910 may, for example, share any or all characteristics with anycommunication network node (or portion thereof) discussed herein.

In accordance with various aspects of the present disclosure, an MCN 910may for example comprise resources (e.g., processing resources, memoryresources, communication resources, sensor and/or sensor accessresources, energy resources, mobility resources, vehicle systemresources, etc.) that are unutilized or underutilized. As discussedherein, such resources may be utilized to host applications, which mayin-whole or in-part be distributed throughout a vehicle communicationnetwork or IMT (e.g., to one or more of the various nodes of the vehiclecommunication network or IMT, etc.).

The MCN 910 may, for example, recognize that its resources areunderutilized and/or a central controller (or CVG) may (e.g., throughmonitoring information flowing from and/or to the MCN 910, etc.)recognize that the MCN 910 has one or more resources that areunderutilized. The MCN 910 may, for example, offer the utilization ofany one or more of its resources to the CVG (e.g., by sending a messageto the CVG through the vehicle communication network or any othercommunication network path discussed herein, etc.) and/or the CVG mayrequest (or demand) the utilization of any one or more resources of theMCN 910 (e.g., by sending a message to the MCN 910 through the vehiclecommunication network or any other communication network path discussedherein).

In an example implementation, in addition to availability of variousresources (e.g., processing resources, memory resources, etc.) the MCN910 may have access to data available only locally to the MCN 910 in thecontext of application execution at the MCN 910, thus providing valuablelow-latency access to various data sources (e.g., sensors on-board avehicle, sensors in general proximity of a vehicle's current location,information directly from an autonomous vehicle control system, etc.).

The example MCN 910 of FIG. 9 may, for example, include variousfunctional modules (e.g., software or firmware code implemented by oneor more processors thereof, etc.) that operate to perform the variousMCN 910 functionalities discussed herein.

For example, the MCN 910 may, for example, comprise a Container Manager915 (or Container Manager Module) that operates to manage the executionof the application code received from the CVG. An example of such aContainer Manager 915 and/or the operation thereof is presented U.S.patent application Ser. No. 15/616,337, filed Jun. 7, 2017, and titled“SYSTEMS AND METHODS FOR MANAGING CONTAINERS IN A NETWORK OF MOVINGTHINGS,” the entirety of which is hereby incorporated herein byreference for all purposes. The Container Manager 915 may, for example,utilize the Communications and Data Manager Module 920 to communicatewith the CVG, other nodes of the Cloud, other nodes of the vehiclecommunication network, etc.

The MCN 910 may, for example, comprise a local Billing Module 925 thatoperates to collect and measure the executed credits (or cost or othermeasure) based on the system usage and data consumption, for example asmay be monitored by the Resource Monitor Module 927. The local BillingModule 925 of the MCN 910 may also, for example, operate to BlockChainthe collected billing logs.

The MCN 910 may, for example, comprise Embedded Sensors 930 in thehardware that hosts the MCN 910 system (e.g., embedded in the Mobile APsystem, embedded in the Fixed AP system, etc.). Thus, the MCN 910 (orany module thereof) may have direct access to data associated with suchsensors.

The MCN 910 may also, for example, have communication links (e.g.,direct or indirect communication links, any of the types ofcommunication links discussed herein, etc.) with External Sensors 935,for example sensors outside of the MCN 910 hardware. The MCN 910 (orapplication being executed on the MCN 910) may, for example, pull datafrom such External Sensors 935 and/or such External sensors 935 may pushdata to the MCN 910, depending on the implementation. The MCN 910 and/orthe External Sensors 935 may comprise an API 940 (or other interface)that provides the interface for such communication of sensorinformation.

The MCN 910 may additionally, for example, comprise a smartCommunications and Data Manager 920 (or Communications and Data ManagerModule) that collects and distributes data to the Cloud 950 (e.g., tothe CVG, to any of a variety of Cloud servers, etc.). The Communicationsand Data Manager 920 may, for example, utilize any or all of the mannersof communication discussed herein. For example, the Communications andData Manager 920 may operate to implement immediate real-timecommunication, delay tolerant communication, communication via thevehicle communication network, communication via the cellularinfrastructure, etc. The manner in which the Communications and DataManager 920 communicates may, for example, be indicated by thecorresponding application being executed at the MCN 910 and/or may bedetermined based on the identity of the corresponding application beingexecuted at the MCN 910, etc.

Various aspects of the disclosure will now be demonstrated in thecontext of an application life cycle.

Turning next to FIG. 10, such Figure shows a flow diagram 1000 of anapplication life cycle, in accordance with various aspects of thepresent disclosure. The example life cycle 1000 (or flow or method orsequence) may, for example, share any or all characteristics with theother example methods, systems, networks and/or network components 100,200, 300, 400, 500-570, 600, 700, 800, 900, and 1100, discussed herein.

Developers may, for example at block 1005, develop an application usinga well-defined structure (e.g., provided by the CVG) that can beenforced by the use of an Integrated Development Environment (IDE)and/or Graphical User Interface (GUI). The application definition may,for example, define (or specify) the types of local data to which theapplication subscribes. The application definition may also, forexample, define (or specify) the local operations that are to beperformed by the MCN (and/or the CVG or other node) on data that isobtained locally. The application definition may additionally, forexample, define (or specify) the types of global data to which theapplication subscribes (e.g., combination of locally acquired data, datafrom other data sources that are available in the Cloud/Internet, datafrom other MCNs, data fusion, etc.). The application definition mayfurther, for example, define (or specify) the global operations that areto be performed by the MCN (and/or the CVG or other node) on the globaland/or local data.

The developed application may, for example at block 1010, be uploaded tothe Application Upload Manager (AUM) of the CVG. As discussed herein,the AUM may then, for example at block 1015, perform a set of tests tovalidate the format and other aspects of the application, and map therequirements of the uploaded application.

When the application is uploaded, the developer may for example definevarious requirements and characteristics of the application. Forexample, the developer may specify computation capability that isnecessary (or desired), execution priority for the application (e.g.,relative to other applications and/or responsibilities of the MCN,etc.), scheduling and duration of execution of the application,identification of the applications (or portions thereof) that may beexecuted in an MCN, etc.

The CVG may, for example at block 1020, analyze the billing to check therequired resources against the available credits that the developer hasin the system.

The CVG may, for example, perform a defined procedure in the Mapper,which may comprise extracting the required computation capacity,extracting the local and global data sources to which the applicationwill subscribe, extracting the code that will be executed locally (e.g.,VNAS Local code, etc.), extracting the code that will be executed whenthe data is received back in the Cloud (e.g., VNAS data-event code,etc.), and extracting the code that will be executed when thecomputation ends and all data is received (e.g., VNAS wrapping code,etc.).

The Mapper may then, for example at block 1025, define the period of theexecution of the application, for example first in the entire pool ofavailable MCNs as well as in a per-instance basis of each MCN.

The period of execution per basis and per pool may, for example, be afunction, but non-exclusively, of: available resources, paid credits tohave priority in the access to resources, general evaluation of code tobe executed, and expected duration of execution.

The CVG may then, for example, send the application to the Scheduler,which may then manage the provisioning of the application in (or to) theavailable resources during the selected duration of execution.

After the application is distributed among the allotted MCNs (e.g., atblock 1030) and scheduled for local execution at the MCN(s) (e.g., atblock 1055), the application may then begin executing (e.g., at block1040), and consuming the local MCN resources that were defined by theScheduler. During the period of execution, data can (e.g., at block1042) be sent in real-time or in a delay-tolerant manner, to theHarvester. The periodicity and priority of the data may, for example, bedefined by the developer while developing the application. Also,additional data can be defined (or specified to be sent to the Harvesterafter the period of execution terminates). Further, operational data forCVG/MCN operation may be communicated that is outside the control of theapplication developer.

As discussed herein, the available capacity of the network (e.g., ofMCNs, etc.) for computing and for data may be calculated. For example,to determine the existing capacity of the network, the MCNs maycommunicate various types of information back to the Harvester in theCVG. Such information may, for example, comprise information indicatingpresently (and/or predicted) available processor (or CPU) capacity,memory load, disk space, etc.

Additionally, the MCNs may also publish the data sources that areavailable (e.g., directly available to the MCN, indirectly available tothe MCN through other nodes, etc.). Data sources may, for example,include all data that is available in (or to) the MCNs either by beingprovided directly by the host hardware, acquired from the IoT (or othernodes) or in-vehicle sensors that publish their data to the MCN, etc.Some data sources may, for example, be available only in specificlocations, for example along the route and/or coverage area of an MCN,may be available only from a vehicle carrying the MCN, etc.

As discussed herein, various aspects of the present disclosure concernperforming billing for the services provided. For example, due to thelimited capacity of the network, and also for example to enable a numberof business cases to be run on top of a system as described herein,billing may be applied to any or all scheduled and distributedapplications. Each developer may, for example, have access to a numberof credits that are earned by payment of a specific fee or awarded basedon any of a variety business criteria. Credits may, for example, be usedto provide rightful access to the existing computation and data capacityof the network. For example, when the execution of an application isbeing managed by the CVG, the Billing module may (e.g., at block 1045)compute the total credit cost of executing such application based on acost function. The cost function may consider any of a variety ofcriteria or factors, for example: amount of total computation capabilityneeded (e.g., total number of MCNs needed, total amount of particularresources needed, etc.), priority of execution, priority of developer,expected scheduling and duration of execution, data sources subscribed,amount of data that is transmitted in real-time, amount of data that istransmitted after the period of execution, etc.

Additionally, each of the MCNs may also track (and/or log) the usedresource capacity by each of the executing (or running) applications. Inan example implementation, to ensure that the billing log is notcompromised, a BlockChain sequence is used. Billing logs may then, forexample at block 1050, be sent to the CVG as soon as the localcomputation is complete. The CVG may then, for example, validate theBlockChain in each of the billing logs received from the multipleallocated MCNs and confirm the total number of credits used.

In an example implementation, the applications developed may leveragestructured programming language that provides various capabilities. Suchcapabilities may, for example, comprise the ability to contain a generalplain text description of the application functionality; host code thatcan be run asynchronously; subscribe to CVG libraries and APIs in orderto use general functions to subscribe and upload data as well as othersystem-wide functions; define what data and results need to be updatedin real-time, in a delay-tolerant fashion, and after the execution ofthe application; define the criteria for the end of the execution of theapplication; define the code that should be executed during and afterthe execution of the application; describe the number ofdeveloper-defined tests for the application, etc.

Systems and methods implemented in accordance with various aspects ofthe present disclosure may provide a variety of benefits. For example,such systems and methods may make use of excess computation capacity inMCNs (e.g., Mobile APs, Fixed APs, other mobile nodes, etc.), providingpart of the Internet of Moving Things to developers and applications asa computation service. Also for example, such systems and methods maymake use of the data sources from which data collection is possible fromMCNs (e.g., Mobile APs, Fixed APs, other mobile nodes, etc.), providingpart of the Internet of Moving Things to developers and applications asa data service. Additionally for example, such systems and methods maymake the excess computation capacity and new data sources available withfair access to all developers and applications. Further for example,such systems and methods may map global rules and requirements to localdecisions, for example to optimize the usage of the networkedcomputation capacity.

To reduce the total amount of data that needs to be transmitted to theCloud, systems and methods implemented in accordance with variousaspects of this disclosure provide a systematic way of performing atleast some of the computation closer in the network to where the data isacquired, reducing the latency to access data as well as the networkusage, while making use of the underutilized capacity of the systems inthe Internet of Moving Things.

The systems and methods discussed herein may be beneficially utilized inany of a variety of implementations and environments. Such example, suchimplementations may include stitching between sensors (e.g., localsensor fusion) such as Lidar, Radar and Cameras for 3D Mapping; smartcity applications that require massive computing at a lower cost; andautonomous vehicle applications that require very low latency forcomputation.

MCNs may, for example, make use of further distribution of thecomputation capacity to other MCNs in their vicinity. For example, anMCN may perform any or all of the CVG functionality discussed herein(albeit at a local level) with regard to neighboring MCNs. Also forexample, MCNs can run offline computation and use delay tolerantnetworking to distribute and acquire both applications and data.

IDE and GUI technology may be utilized for application developmentsandboxing and virtualization.

Also, as discussed herein, a CVG can predict the available capacity ofthe MCNs and available data sources based on past data and machinelearning.

As discussed herein, any or all of the functionality may be performed ina CVG, MCN, or other network node. An example block diagram of such anetwork node is provided at FIG. 11.

Turning next to FIG. 11, such figure shows a block diagram of variouscomponents of an example network node, in accordance with variousaspects of the present disclosure. The example network node 1100 may,for example, share any or all characteristics with the other examplenetworks (and/or network components and/or methods) 100, 200, 300, 400,500-570, 600, 700, 800, 900, and 1000, discussed herein.

The network node 1100 may, for example, comprise any of the networknodes discussed herein, for example a CVG, an MCN (e.g., an access point(AP) node (e.g., a Mobile AP, a Fixed AP, etc.), a Network Controllernode, a Cloud server and/or database, etc. The example node 1100 maycomprise a variety of components (or modules), non-limiting examples ofwhich are provided herein. Note that the CVG and/or MCN functionality(or any portion thereof) may be integrated into any of the communicationnodes discussed herein, but may also be an independent entity.

The example node 1100 may, for example, comprise a communicationinterface (I/F) module 1120 (e.g., including a cellular communicationinterface module, mobile network communication interface module, Wi-Ficommunication interface module, user/client communication interfacemodule, etc.) that operates to perform any or all of the wireless and/orwired communication functionality for the node 1100, many examples ofwhich are provided herein (e.g., communication with sensors external to(or of) the node 1100, communication with the onboard diagnostic (OBD)system of a vehicle in which the node 1100 is installed, communicationwith peer nodes, communication with Mobile APs and/or Fixed APs,communication with Network Controllers, communication with clientdevices, backhaul communication, Cloud server communication, etc.). Thecommunication interface (I/F) module 1120 may, for example, operate inaccordance with any of a variety of cellular communication protocols,3G, 4G, LTE, wireless LAN communication protocols (e.g., Wi-Fi, etc.),wireless PAN communication protocols (e.g., Bluetooth, etc.), 802.11p orDSRC, satellite communication protocols, fiber or cable communicationprotocols, LAN protocols (e.g., Ethernet, etc.), TCP/IP, etc.

The example node 1100 may, for example, comprise any of the MCN and/orCVG modules 1130 discussed herein.

The example node 1100 may, for example, comprise a Master Control Module1110 that generally manages operation of the node 1100 at a high level.Such Master Control Module 1110 may, for example, comprise variousaspects of an operating system for the node 1100.

The example node 1100 may further, for example, comprise one or moreapplications 1150 executing on the node 1100 (e.g., CVG applications,MCN applications, sensor interface applications, mesh networkingapplications, etc.). Any or all of the applications 1150 may, forexample, utilize (e.g., communicate with) the MCN and/or CVG Modules1130 for any or all of the MCN and/or CVG functionality discussedherein. For example, any or all of the applications 1150 may interactwith the MCN and/or CVG Modules 1130 in any of the manners discussedherein.

The example node 1100 may also comprise one or more processors 1180 andmemory devices 1190. The processor(s) 1180 may, for example, compriseany of a variety of processor characteristics. For example, theprocessor(s) 1180 may comprise one or more of a general purposeprocessor, RIS processor, microcontroller, ASIC, DSP, video processor,etc. The memory device(s) 1190 may, for example, comprise any of avariety of memory characteristics. For example, the memory device(s)1190 may comprise a volatile memory, non-volatile memory, etc. Thememory device(s) 1190 may, for example, comprise one or more harddrives, memory chips, etc. The memory device(s) 1190 may, for example,comprise a non-transitory computer-readable (or machine-readable) mediumthat comprises software instructions that when executed by theprocessor(s) 1180, cause the node 1100 (or modules or entities thereof)to perform any or all of the functionality discussed herein (e.g., withregard to the example methods discussed herein, etc.). The memorydevice(s) 1190 may, for example, store media content information, nodeinformation, distribution function information, scheduling information,harvested information, sensor information, any or all of the types ofinformation discussed herein, etc. The memory device(s) 1190 may also,for example, store any or all of the client list and/or topic listinformation discussed herein.

As explained herein, the functionality (e.g., MCN and/or CVGfunctionality, etc.) discussed herein may be performed in a single node,for example any or all of the nodes discussed herein, but may also beperformed in a distributed manner in which respective portions of thefunctionality discussed herein are performed by respective nodes.

In accordance with various aspects of this disclosure, examples of thenetworks and/or components thereof presented herein are provided in U.S.Provisional Application Ser. No. 62/222,192, titled “CommunicationNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

In accordance with various aspects of this disclosure, the networksand/or components thereof presented herein are provided with systems andmethods for integrating such networks and/or components with othernetworks and systems, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/221,997, titled “IntegratedCommunication Network for A Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for synchronizing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,016, titled “Systems and Methods forSynchronizing a Network of Moving Things,” filed on Sep. 22, 2015, whichis hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,042, titled “Systems and Methods forManaging a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for monitoring such networks and/or components,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/222,066, titled “Systems and Methods forMonitoring a Network of Moving Things,” filed on Sep. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for detecting and/or classifying anomalies insuch networks and/or components, non-limiting examples of which areprovided in U.S. Provisional Application Ser. No. 62/222,077, titled“Systems and Methods for Detecting and Classifying Anomalies in aNetwork of Moving Things,” filed on Sep. 22, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,098, titled “Systems and Methodsfor Managing Mobility in a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing connectivity in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,121, titled “Systems and Methodsfor Managing Connectivity a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for collecting sensor data in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,135, titled “Systems and Methodsfor Collecting Sensor Data in a Network of Moving Things,” filed on Sep.22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for interfacing with such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,145, titled “Systems and Methodsfor Interfacing with a Network of Moving Things,” filed on Sep. 22,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for interfacing with a user of such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,150, titled “Systems and Methodsfor Interfacing with a User of a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for data storage and processing in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,168, titled “Systems and Methodsfor Data Storage and Processing for a Network of Moving Things,” filedon Sep. 22, 2015, which is hereby incorporated herein by reference inits entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for vehicle traffic management in such networksand/or components, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,183, titled “Systems and Methodsfor Vehicle Traffic Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for environmental management in such networks and/orcomponents, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/222,186, titled “Systems and Methodsfor Environmental Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing port or shipping operation in suchnetworks and/or components, non-limiting examples of which are providedin U.S. Provisional Application Ser. No. 62/222,190, titled “Systems andMethods for Port Management in a Network of Moving Things,” filed onSep. 22, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of positioning orlocation information based at least in part on historical data,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/244,828, titled “Utilizing Historical Data toCorrect GPS Data in a Network of Moving Things,” filed on Oct. 22, 2015,which is hereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing the accuracy of position or locationof positioning or location information based at least in part on theutilization of anchors, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/244,930, titled “Using Anchorsto Correct GPS Data in a Network of Moving Things,” filed on Oct. 22,2015, which is hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing communication between applications,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/246,368, titled “Systems and Methods forInter-Application Communication in a Network of Moving Things,” filed onOct. 26, 2015, which is hereby incorporated herein by reference in itsentirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for probing, analyzing and/or validatingcommunication, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/246,372, titled “Systems and Methodsfor Probing and Validating Communication in a Network of Moving Things,”filed on Oct. 26, 2015, which is hereby incorporated herein by referencein its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for adapting communication rate, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/250,544, titled “Adaptive Rate Control for Vehicular Networks,” filedon Nov. 4, 2015, which is hereby incorporated herein by reference in itsentirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for reconfiguring and adapting hardware,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/273,878, titled “Systems and Methods forReconfiguring and Adapting Hardware in a Network of Moving Things,”filed on Dec. 31, 2015, which is hereby incorporated herein by referencein its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for optimizing the gathering of data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/253,249, titled “Systems and Methods for Optimizing Data Gathering ina Network of Moving Things,” filed on Nov. 10, 2015, which is herebyincorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing delay tolerant networking,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/257,421, titled “Systems and Methods for DelayTolerant Networking in a Network of Moving Things,” filed on Nov. 19,2015, which is hereby incorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for improving the coverage and throughput ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/265,267, titled “Systems andMethods for Improving Coverage and Throughput of Mobile Access Points ina Network of Moving Things,” filed on Dec. 9, 2015, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for coordinating channel utilization, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,858, titled “Channel Coordination in a Network of Moving Things,”filed on Dec. 22, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for implementing a network coded mesh network in thenetwork of moving things, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/257,854, titled “Systems andMethods for Network Coded Mesh Networking in a Network of MovingThings,” filed on Nov. 20, 2015, which is hereby incorporated herein byreference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for improving the coverage of fixed access points,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/260,749, titled “Systems and Methods forImproving Fixed Access Point Coverage in a Network of Moving Things,”filed on Nov. 30, 2015, which is hereby incorporated herein by referencein its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing mobility controllers and their networkinteractions, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/273,715, titled “Systems and Methodsfor Managing Mobility Controllers and Their Network Interactions in aNetwork of Moving Things,” filed on Dec. 31, 2015, which is herebyincorporated herein by reference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for managing and/or triggering handovers ofmobile access points, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/281,432, titled “Systems andMethods for Managing and Triggering Handovers of Mobile Access Points ina Network of Moving Things,” filed on Jan. 21, 2016, which is herebyincorporated herein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing captive portal-related control andmanagement, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/268,188, titled “CaptivePortal-related Control and Management in a Network of Moving Things,”filed on Dec. 16, 2015, which is hereby incorporated herein by referencein its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for extrapolating high-value data, non-limitingexamples of which are provided in U.S. Provisional Application Ser. No.62/270,678, titled “Systems and Methods to Extrapolate High-Value Datafrom a Network of Moving Things,” filed on Dec. 22, 2015, which ishereby incorporated herein by reference in its entirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote software updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/272,750, titled “Systems and Methodsfor Remote Software Update and Distribution in a Network of MovingThings,” filed on Dec. 30, 2015, which is hereby incorporated herein byreference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for providing remote configuration updating anddistribution, non-limiting examples of which are provided in U.S.Provisional Application Ser. No. 62/278,662, titled “Systems and Methodsfor Remote Configuration Update and Distribution in a Network of MovingThings,” filed on Jan. 14, 2016, which is hereby incorporated herein byreference in its entirety.

Still further, in accordance with various aspects of this disclosure,the networks and/or components thereof presented herein are providedwith systems and methods for adapting the network, for exampleautomatically, based on user feedback, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,243, titled“Systems and Methods for Adapting a Network of Moving Things Based onUser Feedback,” filed on Jan. 22, 2016, which is hereby incorporatedherein by reference in its entirety.

Yet further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for enhancing and/or guaranteeing data integritywhen building or performing data analytics, non-limiting examples ofwhich are provided in U.S. Provisional Application Ser. No. 62/278,764,titled “Systems and Methods to Guarantee Data Integrity When BuildingData Analytics in a Network of Moving Things,” Jan. 14, 2016, which ishereby incorporated herein by reference in its entirety.

Also, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for performing self-initialization and/or automatedbootstrapping of mobile access points, non-limiting examples of whichare provided in U.S. Provisional Application Ser. No. 62/286,515, titled“Systems and Methods for Self-Initialization and Automated Bootstrappingof Mobile Access Points in a Network of Moving Things,” filed on Jan.25, 2016, which is hereby incorporated herein by reference in itsentirety.

Additionally, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for managing power supply and/or utilization,non-limiting examples of which are provided in U.S. ProvisionalApplication Ser. No. 62/295,602, titled “Systems and Methods for PowerManagement in a Network of Moving Things,” filed on Feb. 16, 2016, whichis hereby incorporated herein by reference in its entirety.

Further, in accordance with various aspects of this disclosure, thenetworks and/or components thereof presented herein are provided withsystems and methods for automating and easing the installation and setupof the infrastructure, non-limiting examples of which are provided inU.S. Provisional Application Ser. No. 62/299,269, titled “Systems andMethods for Automating and Easing the Installation and Setup of theInfrastructure Supporting a Network of Moving Things,” filed on Feb. 24,2016, which is hereby incorporated herein by reference in its entirety.

In summary, various aspects of this disclosure provide communicationnetwork architectures, systems and methods for supporting a network ofmobile nodes. As a non-limiting example, various aspects of thisdisclosure provide communication network architectures, systems, andmethods for managing resource utilization in a network of moving things,for example including autonomous vehicles. While the foregoing has beendescribed with reference to certain aspects and examples, it will beunderstood by those skilled in the art that various changes may be madeand equivalents may be substituted without departing from the scope ofthe disclosure. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the disclosurewithout departing from its scope. Therefore, it is intended that thedisclosure not be limited to the particular example(s) disclosed, butthat the disclosure will include all examples falling within the scopeof the appended claims.

What is claimed is:
 1. A vehicle communication network comprising: awireless access point (AP) comprising: at least one AP transceiver; anAP processor and memory; and at least one module operable to, at least:utilize the at least one AP transceiver to provide wireless networkconnectivity to other devices within communication range of the wirelessAP; utilize the at least one AP transceiver to receive an application;and execute the application; and a second node comprising: a second nodeprocessor and memory; and at least one module operable to, at least:receive the application from an application source; determine a level ofavailability of a sharable resource of the wireless AP; determine, basedat least in part on the determined level of availability of the sharableresource of the wireless AP, whether to map the application to thewireless AP; and if it is determined to map the application to thewireless AP, then: communicate the application to the wireless AP forexecution by the wireless AP; and during execution of the application bythe wireless AP, control execution of the application by the wirelessAP.
 2. The vehicle communication network of claim 1, wherein thewireless AP is mobile.
 3. The vehicle communication network of claim 1,wherein the at least one module of the second node is operable toschedule execution of the application by the wireless AP.
 4. The vehiclecommunication network of claim 1, wherein the at least one module of thesecond node is operable to, during execution of the application by thewireless AP: monitor the level of availability of the sharable resourceof the wireless AP; and adjust the execution of the application by thewireless AP based, at least in part, on the monitored level ofavailability.
 5. The vehicle communication network of claim 1, whereinthe at least one module of the second node is operable to: determine alocation of the wireless AP; and determine whether to map theapplication to the wireless AP based, at least in part, on thedetermined location of the wireless AP.
 6. The vehicle communicationnetwork of claim 5, wherein the wireless AP is a Mobile AP, and the atleast one module of the second node is operable to: determine atrajectory of the wireless AP; and determine whether to map theapplication to the wireless AP based, at least in part, on thedetermined trajectory of the wireless AP.
 7. The vehicle communicationnetwork of claim 1, wherein: the at least one module of the wireless APis operable to utilize the at least one transceiver of the wireless APto communicate a message comprising information identifying the level ofavailability of the sharable resource of the wireless AP; and the atleast one module of the second node is operable to: receive the messagefrom the wireless AP; and determine the level of availability of thesharable resource of the wireless AP based, at least in part, oncontents of the message.
 8. The vehicle communication network of claim1, wherein the sharable resource of the wireless AP comprises a datasource external to the wireless AP to which the wireless AP has access.9. The vehicle communication network of claim 8, wherein the data sourcecomprises a sensor.
 10. The vehicle communication network of claim 8,wherein the data source comprises an on-board system of a vehicle thatis carrying the wireless AP.
 11. The vehicle communication network ofclaim 1, comprising a second wireless AP, wherein the at least onemodule of the second access point is operable to transition execution ofthe application from the wireless AP to the second wireless AP based, atleast in part, on a location of the wireless AP and on a location of thesecond wireless AP.
 12. The vehicle communication network of claim 1,comprising a second wireless AP, wherein the at least one module of thesecond access point is operable to transition execution of theapplication from the wireless AP to the second wireless AP based, atleast in part, on a trajectory of the wireless AP and on a trajectory ofthe second wireless AP.
 13. A wireless access point (AP) for use in avehicle communication network, the wireless AP comprising: at least onetransceiver; a processor and memory; and at least one module operableto, at least: utilize the at least one transceiver to provide wirelessnetwork connectivity to other devices within communication range of thewireless AP; utilize the at least one transceiver to communicate firstinformation to a second system via at least the vehicle communicationnetwork, wherein the first information comprises information identifyinga level of availability of a sharable resource of the wireless AP; andin response to, at least, the communicated first information, at least:utilize the at least one transceiver to receive an application from thesecond system to execute utilizing the sharable resource; and executethe application under control of the second system.
 14. The wirelessaccess point (AP) of claim 13, wherein the wireless AP is mobile. 15.The wireless access point (AP) of claim 13, wherein the at least onemodule is operable to, during execution of the application, utilize theat least one transceiver to communicate second information to the secondsystem via at least the vehicle communication network, wherein thesecond information comprises updated information identifying the levelof availability of the sharable resource.
 16. The wireless access point(AP) of claim 13, wherein the at least one module is operable to utilizethe at least one transceiver to: communicate second information to thesecond system, wherein the second information comprises informationidentifying a location of the wireless AP; and receive the applicationfrom the second system in response also to the communicated secondinformation.
 17. The wireless access point (AP) of claim 16, wherein theat least one module is operable to utilize the at least one transceiverto: communicate third information to the second system, wherein thethird information comprises information identifying a trajectory of thewireless AP; and receive the application from the second system inresponse also to the communicated third information.
 18. The wirelessaccess point (AP) of claim 13, wherein the at least one module isoperable to: monitor utilization of the sharable resource by theapplication; and utilize the at least one transceiver to communicateutilization information to the second system regarding the monitoredamount of utilization.
 19. The wireless access point (AP) of claim 13,wherein the sharable resource of the wireless AP comprises a data sourceexternal to the wireless AP to which the wireless AP has access.
 20. Anetwork node for use in a vehicle communication network, the networknode comprising: a processor and memory; and at least one moduleoperable to, at least: receive an application from an applicationsource; determine a level of availability of a sharable resource of awireless AP of the vehicle communication network; determine, based atleast in part on the determined level of availability of the sharableresource of the wireless AP, whether to map the application to thewireless AP; and if it is determined to map the application to thewireless AP, then: communicate the application to the wireless AP forexecution by the wireless AP; and during execution of the application bythe wireless AP, control execution of the application by the wirelessAP.
 21. The network node of claim 20, wherein the at least one module isoperable to, during execution of the application by the wireless AP:monitor the level of availability of the sharable resource of thewireless AP; and adjust the execution of the application by the wirelessAP based, at least in part, on the monitored level of availability. 22.The network node of claim 20, wherein the at least one module isoperable to: determine a location of the wireless AP; and determinewhether to map the application to the wireless AP based, at least inpart, on the determined location of the wireless AP.
 23. The networknode of claim 20, wherein the at least one module of the second accesspoint is operable to transition execution of the application from thewireless AP to a second wireless AP of the vehicle communication networkbased, at least in part, on a location of the wireless AP and on alocation of the second wireless AP.